Search documents

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

The description mentions it 'returns short summaries', but does not disclose whether the tool is read-only, requires authentication, has rate limits, or any side effects. With no annotations provided, the description carries the full burden for behavioral disclosure and falls short.

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?

The description is very concise (one sentence) and front-loaded with purpose, but it omits critical information. Conciseness is not valuable when it sacrifices necessary details.

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?

Given the high parameter count (14), no output schema, and no annotations, the description is severely incomplete. It does not explain the required 'kind' parameter, allowed filters, pagination, or output format.

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?

With 14 parameters and 0% schema description coverage, the description offers no parameter-level details. The phrase 'by business filters' is too vague to help an agent understand which parameters are available or their purpose.

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?

The description clearly states the verb 'Search', the resource 'accounting documents', and the output 'short summaries'. However, it does not differentiate from sibling tools like 'search_overdue_items' or 'search_unpaid_documents', which similarly search for specific document types.

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 is provided on when to use this tool versus alternatives. There are no prerequisites, exclusions, or contextual hints about which business scenario this tool is best suited for.

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