search

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

Discloses that it automatically detects emails, IDs, or falls back to metadata/name filtering, which helps the agent understand how queries are interpreted. No annotations provided, but the description adequately describes non-destructive search 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?

Two concise sentences that front-load the purpose and add key behavioral detail without any 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?

Given the simple nature of the tool (2 parameters, no output schema), the description sufficiently covers what it searches and how queries are processed. Missing mention of result format but acceptable for a search 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% with descriptions, and the description adds value by explaining how the query parameter is interpreted (auto-detection of types).

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 it performs a lightweight unified search across Accounts, Subscriptions, and Invoices, which is specific and distinguishes it from sibling tools that target individual entities.

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?

Implicitly suggests this is for broad searches when you don't know the exact entity type, but lacks explicit guidance on when to prefer alternatives like get-account-by-email or list-* tools.

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