Search records

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

The description claims that 'Query or filter is required', but the input schema has zero parameters, creating a direct contradiction. No annotations are provided to clarify behavior.

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?

While short, the description omits critical details and contradicts the schema. Conciseness is not beneficial when it sacrifices completeness and accuracy.

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?

With no output schema and no annotations, the description fails to explain how to invoke the tool or interpret results. It is incomplete for a tool with zero parameters but claimed required inputs.

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?

The input schema has no parameters (100% coverage), yet the description asserts required query/filter. This misleads the agent; no meaningful parameter information is added.

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 states 'Search one evidence and return short record summaries', but the term 'evidence' is vague and not defined. It does not differentiate from sibling tools like search_documents or search_partners. The purpose is unclear.

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 is no mention of prerequisites or exclusions.

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