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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: what the result contains (vendors, in-house approaches, effort/cost signals, source disclosure) and the editorial neutrality policy ('does not accept payment', 'does not rank or endorse'). It stops short of 5 only because return formatting/pagination is unaddressed.

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?

Three tightly written sentences: the operation and its scope come first, the payload description second, and the trust/neutrality caveat last. No sentence is filler and nothing is buried.

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 correctly takes on the burden of saying what comes back, and annotations handle the safety profile. The only unaddressed items are the optional jurisdiction filter's effect and result volume/pagination, which are minor for a catalog lookup.

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%, with controlId format and jurisdiction semantics fully documented in the schema, so the baseline is 3. The description only restates the controlId precondition and never mentions the jurisdiction filter or how region matching behaves, adding no meaning beyond the schema.

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 gives a specific verb and resource ('list third-party vendors and in-house approaches') scoped by a Control id, and it even characterizes the payload ('effort/cost signals and a source-disclosure'). It does not differentiate itself from siblings like find_controls or find_counsel, which also operate on the compliance catalog, so it stops short of a 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?

Usage is only implied via the input precondition ('Given a Control id') and the framing sentence 'Returns a neutral catalog for research; evaluate fit independently.' There is no explicit when-to-use vs. when-not, and no alternative tool (e.g. find_controls for discovering the controlId first) is named.

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