search_acme_account_keys

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Search' is consistent. It adds no additional behavioral side effects (e.g., auth needs, rate limits) beyond what annotations already convey. The 'filtering and pagination' mention is a functional detail, not a behavior disclosure.

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?

The description is a single concise sentence that communicates the core purpose and key features without any filler, making it optimally front-loaded and efficient.

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 read-only search tool with four optional parameters, comprehensive schema descriptions, and an output schema, the description is adequate. It covers the essential purpose, but could benefit from mentioning default sorting/pagination behavior or the client-side filter nature of search_term (though schema already notes this). Overall, sufficient.

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 all four parameters described (page, sort_by, page_size, search_term). The description adds no parameter-specific semantics beyond the generic 'filtering and pagination', relying entirely on the schema for meaning.

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 action ('Search'), the resource ('ACME account keys'), and the key features ('filtering and pagination'). This directly distinguishes it from sibling tools like 'create_acme_account_key' and 'get_acme_settings'.

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 description implies usage for searching/listings but provides no explicit guidance on when to use it versus alternatives. No exclusions or alternative tool mentions are given, so the context is inferred rather than stated.

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