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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond them: the entries include status, as-of date, issuer and confidence grade, and it explicitly caps the tool's scope at the catalogue with no interpretive output. It does not discuss pagination, but for a read-only lookup that is minor.

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?

Front-loaded with labeled sections (Purpose, Guidelines, Limits, Ex) so an agent can scan purpose first and constraints last. It is somewhat long, but every block contributes routing, boundary, or example value rather than filler.

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?

With an output schema present, return-value explanation is unnecessary. Purpose, when-to-use, explicit scope limit, entry fields, and example calls together give an agent everything needed to call this 4-parameter optional tool correctly.

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 description coverage is 100%, so baseline is 3. The description goes further by giving concrete invocations that illustrate how status and keyword are actually used (status='withdrawn', keyword='14067'), clarifying intent beyond the schema's field-level text.

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 a specific resource (the carbon accounting standards library) and enumerates its contents (ISO 14064 series, ISO 14067, ISO 14068-1, GHG Protocol, withdrawn standards like PAS 2050) with the fields each entry carries. This clearly separates it from sibling catalogue tools such as get_standards_roadmap or get_policy.

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 names when to use it (questions about which standard governs an organisation-level inventory, a product carbon footprint, or a verification statement), an operational filter tactic (status='withdrawn' to check whether a standard still applies), and an explicit boundary (catalogue only, no interpretation for a specific company).

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