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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot convey: a flat 5-point cost per successful run, which lets an agent weigh the call against cheaper alternatives.

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 tight sentences: the capability and its return fields come first, the cost note second. No filler, no restatement of the tool name, and the most decision-relevant information is front-loaded.

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 indicating what comes back and does so (vendor, ratings, company profile), plus cost. It is nearly complete for a single-parameter read tool; only the exact return shape and failure behavior on an unknown alias are unstated.

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?

There is one parameter with 100% schema description coverage, so the baseline is 3. The description's 'alias or URL' phrasing aligns with and slightly reinforces the schema's example ('forcepoint-dlp') but adds no new format or validation detail.

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 full Gartner Peer Insights product details') and enumerates the payload (vendor, ratings, company profile). The 'by alias or URL' phrasing distinguishes it from the sibling search tool run_gartner_products_search, though no sibling is named explicitly.

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 single-identifier lookup form implies 'use when you already have an alias or URL', but the description never states when to prefer this over run_gartner_products_search or run_gartner_market_products. Usage is inferable rather than stated.

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