search_states

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

With no annotations, the description must include behavioral traits. It mentions case-insensitivity but does not disclose return format, pagination, or behavior when no matches are found. Adequate but not comprehensive.

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?

A single, front-loaded sentence that is perfectly concise. Every word serves a purpose, with no redundancy.

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?

For a simple search tool with one required parameter and no output schema, the description is mostly complete. It explains the search criterion and case-insensitivity, though it could mention the return type (e.g., list of state names) for full clarity.

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 schema covers the parameter 'query' with 'Search term'. The description adds the important detail of case-insensitivity, providing value beyond the schema. No other parameters exist.

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' and the resource 'states', and specifies the search is by name and case-insensitive. This effectively distinguishes it from sibling tools like 'get_states' (retrieves all) and 'get_state' (by ID).

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 explicit guidance on when to use this tool versus alternatives such as 'search_actors' or 'get_states'. The description implies usage for name-based searching but does not provide when-not or context for exclusivity.

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