get_standard

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

With no annotations, the description carries the full burden. It discloses that summaries have an as_of date and advises verification, which adds behavioral context. However, it does not mention that the tool is read-only, nor any other behavioral traits like authorization requirements or side effects.

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 concise with two sentences. It presents the core purpose immediately and adds a critical caution efficiently. No extraneous information.

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?

The description covers the basic purpose and data usage warning, but with no output schema, it omits details about the return structure (e.g., fields included in the summary). It also does not mention any constraints on parameter values or error handling.

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 provides 0% description coverage for parameters. The description adds minimal meaning by giving an example (family and name) but does not explain valid values, constraints, or optionality beyond the schema's required fields.

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 'Return a standards summary' with a specific verb and resource. The example 'family=\"ifrs\", name=\"ifrs-16\"' helps disambiguate from sibling tools like 'list_standards' which lists available standards, while this returns a single summary.

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 retrieving a specific standard summary, but does not explicitly state when to use this tool versus alternatives like 'list_standards' or other get_* tools. The caution about verifying the as_of date provides some context but no direct guidance on selection.

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