search_criminal_records

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

With no annotations, the description adds value by disclosing the cost and conditional charging behavior. However, it fails to mention if the operation is read-only, requires authentication, or has rate limits—important for a paid 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?

Extremely concise: two short sentences. All information is front-loaded with the purpose and cost. No wasted 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?

Lacks output schema and does not describe return format, pagination, or failure scenarios. While cost info is useful, the description leaves gaps about what the tool actually returns and how to interpret results, especially important for a paid tool.

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 coverage is 100%, so the schema already documents all parameters. The description adds no new parameter details beyond 'by name', which is already in the schema. Baseline 3 is appropriate; no extra value for parameters.

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 tool searches criminal records by name, with specific verb and resource. It is unambiguous and distinct from siblings like 'find_people' or 'query_lead_database' due to the explicit 'criminal records' domain.

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?

The cost information ('$1 per search, only charged if records found') provides implicit guidance on when to use (when willing to pay for confirmed results) but no explicit when-not-to-use or alternatives. Lacks comparison to other search tools.

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