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

No annotations are provided, so the description carries the transparency burden. It discloses the return content and fields, but it overstates scope by saying 'Returns every catalogued tool' while the schema's `limit` defaults to 15 and caps at 40; it does not surface the default truncation behavior. This mismatch prevents full transparency.

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?

The description is front-loaded with the core promiseasi and then gives a compact use-case and bucket list. The long list of known buckets is justified because `category` has no enum in the schema, though the phrasing could be slightly tighter.

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?

Since there is no output schemahare and no annotations, the description supplies the essential return-value information: leaders/runner-ups/skip candidates, cost, AI-readiness, swap-registry status, and partner sign-up links. It misses only operational nuances like limit defaults and potential truncation, which are partially available in the input schema.

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?

The schema already covers both parameters at 100%, so the baseline is 3. The description adds value by enumerating 21 known bucket values and clarifying that the tool returns a category-wide map, going beyond the schema's short examples. It does not add semantic detail for `limit`, but the schema handles that.

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 ('Returns') and a clear resource ('one GTM category'), and describes the output classes ('leaders, runner-ups, and skip/replace candidates'). It also explicitly contrasts itself with `recommend_partner`, helping an agent distinguish it from a dense sibling list.

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?

Gives direct trigger conditions ('Use when the user wants to see the full landscape'), concrete query examples ('show me all CRMs', 'map the analytics category'), and an explicit alternative (`recommend_partner` is a single best pick). The known bucket list further routes requests to the correct category.

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