IntentusNet provides 4 tools with varying quality. Two tools (fetch_context, update_database) have complete JSON schemas with typed parameters, but descriptions are generic and lack actionable guidance for LLM selection. The 'add' tool has a well-structured schema with parameter descriptions, but minimal overall tool description. 'SearchIntent' lacks input schema visibility and has a bare description. No parameter-level descriptions are visible for fetch_context or update_database. Output schemas are not documented for any tool. Error handling guidance is absent. Tool naming follows verb_noun convention (fetch_*, update_*, add, search_*) which is good, but descriptions do not explain WHEN to use each tool or what makes them distinct from alternatives.

• Expand fetch_context description to: 'Retrieve context data from local cache by key. Use this when you need historical state or session context. Returns either a plain context object or metadata-enriched response if include_metadata=true. Call this before operations that depend on prior state.'
• Add parameter descriptions for fetch_context: context_key → 'Unique key identifying the context record (string, 1-256 chars, alphanumeric + underscore)', include_metadata → 'If true, response includes timestamps, version, and source info. If false, returns only the context data.'
• Expand update_database description to: 'Update a single database record by table and ID. This is a state-changing operation with no automatic rollback, verify arguments before calling. Returns the updated record or an error if validation fails.'
• Add parameter descriptions for update_database: table → 'Target table name (enum: required to be one of: users, contexts, events, config; alphanumeric underscore, max 64 chars)', record_id → 'ID of the record to update (string, must match existing record)', data → 'Object containing only the fields to update; other fields remain unchanged (must be a JSON object; no top-level array)'
• Document update_database output schema: '{ success: boolean, updated_record: object, error?: string }'
• Add confirmation step to update_database: return a dry_run mode that shows what would change without committing, or require explicit confirmation parameter.
• For SearchIntent, provide visible JSON schema: { type: 'object', properties: { query: { type: 'string', description: 'Search query...' } }, required: ['query'] }