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

With no annotations, the description must carry the full behavioral burden. It implies a read-only retrieval and discloses the return content ('full checked facts and sources'), but says nothing about permissions, freshness/verification meaning, or result size — meaningful gaps for an unannotated tool.

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 with an inline concrete example. Nothing wasted, though it is arguably terse enough that a clarifying clause on return shape would have fit without bloat.

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?

There is no output schema, so the description is the only source for what comes back; stating 'full checked facts and sources' partially covers this, but the structure and meaning of 'checked' facts remain unexplained. Adequate but with clear gaps for a tool whose return value is undocumented elsewhere.

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 coverage is 50% (category has no schema description). The description compensates by mapping both parameters through an example ('Clerk in nextjs-auth'), clarifying that category is a slug like nextjs-auth and option is an entry within it. It does not resolve the id-vs-name ambiguity, so it adds moderate but not complete 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 verb and resource: 'Get the full checked facts and sources for one option in a category.' The example ('Clerk in nextjs-auth') makes the resource concrete and distinguishable from siblings like compare and list_categories, though it does not explicitly name those siblings.

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 phrase 'one option in a category' implies the lookup use case versus the sibling 'compare' for multiple options, but no alternative is named and no when/when-not condition is stated. Usage is reasonably inferable but not explicit.

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