sanity_search

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It only mentions full-text search across fields, but fails to disclose read-only nature, performance, pagination behavior, or any side effects. Minimal transparency for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with clear structure, no redundancy. Efficiently conveys core functionality without superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a basic search tool with 3 parameters and no output schema. Missing details on return format, sorting, or fuzzy matching, but sufficient for typical use. Could improve with usage context or expected output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% parameter coverage, but the description adds value by specifying that searchTerm applies to titles, names, descriptions, and body content. This enriches parameter understanding beyond the schema's 'The search term'. Above baseline due to added context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Search' and resource 'documents', specifying fields searched (titles, names, descriptions, body content). It distinguishes from sibling tools like sanity_list_documents and sanity_query by emphasizing full-text search across specific fields, though not explicitly contrasting with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like sanity_query or sanity_list_documents. The description only states what it does without providing context for selection or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.