run_gartner_categories

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

No annotations, so the description carries the full burden. It usefully discloses cost ('Flat 5 points per successful run') and implies a read-only lookup of the full taxonomy, but says nothing about permissions, pagination, or the shape of what comes back.

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?

Two short, front-loaded sentences with no filler; the purpose comes first and the cost note follows. Efficient, though the cost sentence is tangential to selection.

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 zero-parameter taxonomy lookup with no output schema, the description should indicate what the returned taxonomy looks like (list of category/market names and IDs) so an agent knows how to consume it. That return-shape detail is missing, leaving a meaningful gap.

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 tool takes zero parameters, which is the baseline-4 case. Schema coverage is reported at 100% and the empty schema is self-explanatory, so no parameter detail is needed from the description.

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 ('Get') and a specific resource ('Gartner Peer Insights category and market taxonomy'), which distinguishes it from the Gartner siblings that fetch products, vendors, or market searches. It stops short of explicitly contrasting itself with those siblings, so it lands at 4 rather than 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?

No guidance on when to call this versus run_gartner_market, run_gartner_markets_search, or run_gartner_products_search. The likely role of a taxonomy lookup as a prerequisite for category-filtered calls is left entirely to inference.

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