search_standard

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

No annotations provided, so description carries full burden. It discloses sorting order (most-recent first) but omits other behaviors like result format, pagination, error handling, or rate limits. For a search tool, more detail on output structure would be beneficial.

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, front-loaded with purpose and key behavior (sorting). Every sentence adds value 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?

Given low complexity (one param, no output schema, no nested objects), the description is adequate but not complete. It mentions return order but not result structure, limits, or how to paginate. Missing details could leave the agent uncertain about the output format.

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?

Only one parameter 'query' with schema description 'Standard number or keywords, e.g. 'ETSI TS 102 818''. The description adds a helpful example, providing clarity beyond the schema. Schema coverage is 100%, so baseline is 3, but the example elevates it.

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 it searches the ETSI standards catalogue and returns matching standards sorted most-recent first. Verb is specific ('search') and resource is identified ('ETSI standards catalogue'). Distinguishes from siblings like fetch_standard and get_summary which are for individual documents.

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?

Implied usage: use when needing to find standards by query. No explicit guidance on when not to use or alternatives. Sibling tools are listed but no comparison provided, leaving the agent to infer based on names.

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