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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context: the content is paraphrased rather than authoritative standard text, and it spans regulatory artefacts (ISO 14064-3 verification evidence, Vietnam Decree 06 / Decision 42/2026). That expectation-setting goes beyond the structured fields.

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?

A single front-loaded sentence that opens with the core purpose before the topic list, with no filler. The trailing list is dense and slightly run-on, but every element corresponds to a real capability rather than padding.

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, single-enum-parameter guide with no output schema, the description gives an agent enough to decide and invoke correctly, including the important caveat that content is paraphrased. The main residual gap is that it does not state the return shape (prose guidance vs. structured checklist), which matters for a documentation-retrieval 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 description coverage is 0% and there is one enum parameter, so the description must carry the meaning. The comma-separated topics map almost one-to-one onto the enum values and expand them ('vietnam' → Vietnam Decree 06 / Decision 42/2026, 'categories' → boundaries with Scope 1/2/3 cross-walk), which is real added value over the bare enum strings, though the mapping is not labelled explicitly key-to-value.

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 (ISO 14064-1 organization inventory guidance) and qualifies its nature as 'paraphrased, not the standard text', which cleanly separates it from article/standard-text siblings like get_article and list_articles. It enumerates the covered topics, so an agent knows what it will get. It stops short of naming a sibling to route away from, keeping it at 4 rather than 5.

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 topic enumeration implicitly tells the agent when to reach for this tool (e.g., scope 1/2/3 categories, base-year recalculation), but there is no explicit when-to-use/when-not statement and no routing to alternatives such as get_ghg_regulations or check_ghg_inventory_obligation. Usage is inferable rather than stated.

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