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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful disclosure beyond that: every figure carries provenance, and there is an explicit list of what is NOT measured, plus a cost statement ('Free'). This tells the agent about result trustworthiness and scope limits that no annotation conveys.

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?

Purpose and the measured-metrics inventory are front-loaded in the first clause, with caveats (provenance, unmeasured items) and cost following. Mostly economical, though the trailing 'Free, because a specification is a public good' is a slight flourish rather than operational 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?

For a read-only, single-required-param tool with no output schema, the description is complete enough: it enumerates what is returned, flags provenance, and states what is deliberately excluded. An agent has what it needs to call and interpret it 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% and both parameters (slug, context) are thoroughly documented in the schema itself, including the slug format and the intent of context. The description adds no parameter-level detail, so the baseline 3 applies.

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 — a standards body's adoption level — and enumerates the exact metrics returned (published repositories, graduation counts and share, release cadence, contributor count). This clearly distinguishes it from measurement-listing siblings like find_measured_standards and from metric siblings like standard_repositories, though the action verb is implicit (it is a read/retrieve tool).

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 never states when to reach for this tool versus alternatives such as insights_adoption, standard_repositories, or standard_coalition. The only routing hint ('as find_measured_standards returns it') lives in the schema, not the description, and the closing pricing remark is not usage guidance.

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