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

The annotations already establish this as a safe, read-only, idempotent, open-world call, so the description is not obligated to restate that. It adds genuinely useful context the annotations do not: the credit cost ('Flat 5 points per successful run') and the shape of the returned profile. It stops short of describing rate limits or response format details.

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 with no filler, and the resource description is front-loaded ahead of the cost note. Every clause contributes information.

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 single-param read tool with no output schema, the description covers the input form, the nature of the returned data, and the billing implication. It is close to complete, missing only explicit routing against the sibling Gartner search/product tools.

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?

With a single parameter and 100% schema description coverage, the schema already documents the alias/URL and even gives an example ('data-loss-prevention'). The description's 'by alias or URL' merely echoes that, so this is the baseline 3 where schema does the heavy lifting.

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 resource ('Gartner Peer Insights market profile') and enumerates the payload (features, research, lessons learned). It clearly reads as fetching one profile rather than a list or search, but it never names sibling tools like run_gartner_markets_search or run_gartner_market_products to sharpen the distinction.

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 implied by 'by alias or URL' and the singular 'market profile', suggesting a direct lookup rather than a search. However, there is no explicit when-to-use vs alternatives guidance, no mention of when to prefer run_gartner_markets_search for discovery, and no prerequisites or exclusions.

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