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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the description adds real context beyond them: it discloses that the output carries caveats where the machine-readable source disagrees with the body's own published roster, and that the tool is free. That data-quality disclosure is exactly the kind of trait an agent can't infer from annotations, though it stops short of describing completeness or freshness beyond the caveat framing.

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 what the tool returns, then the caveat disclosure, then a terse 'Free.' Every clause earns its place and there is no filler. The trailing one-word sentence is slightly abrupt but functional rather than wasteful.

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 no output schema, the description carries the burden of describing the return, and it does reasonably well by enumerating the entity types returned and flagging the caveat content. Combined with 100% schema coverage and read-only annotations, an agent has enough to call it correctly; only the response shape/pagination remains unspecified.

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 the schema already documents both the required 'slug' (with a concrete example) and the optional 'context' parameter at length. The description adds no parameter-level meaning of its own, which matches the baseline-3 expectation when the schema does the heavy lifting.

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 and enumerates the exact contents it returns: governing bodies and their membership, working groups, member companies, and named people. Clearly distinguishable in spirit from siblings like standard_adoption or governance_report, but it never names a sibling to sharpen the contrast. Clear verb+resource, just short of explicit sibling differentiation.

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?

Usage is only implied — the reader infers you call this to discover who is behind a standard. There is no when-to-use vs. when-not, no mention of alternatives among the many sibling tools (standard_adoption, standard_repositories, governance_report), and no stated prerequisites. The 'Free' note hints at a cost tradeoff but is not framed as selection guidance.

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