search_locations

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

With no annotations, the description carries the burden and reveals the result contents (address fields and phone number) and clarifies the entity type. It could mention pagination defaults or sort behavior, but those are covered in the schema, so this is adequate.

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?

Two sentences that are efficiently front-loaded with the purpose and a sibling distinction. Every sentence adds value, with no redundant or vague wording.

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 search tool with 9 parameters and no output schema, the description covers key contextual aspects: result fields, entity type, and how it differs from flexible assets. It could elaborate on pagination behavior, but the schema describes page size and page number, making this reasonably complete.

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% with descriptions for all 9 parameters, so the schema does the heavy lifting. The description only adds context about result fields, not additional parameter semantics, meriting the baseline 3.

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?

States 'Search for locations (physical addresses/sites) of an organization' with a specific verb and resource, and clearly distinguishes itself from search_flexible_assets by noting locations are a built-in entity.

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?

Explicitly says 'use this rather than search_flexible_assets to look up an organization's address or phone', providing a clear when-not and an alternative. This gives concrete guidance on when to choose this tool.

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