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

With no annotations, the description carries the behavioral burden. It usefully discloses a flat cost of 5 points per successful run and lists the returned profile contents, but it omits auth/permission requirements, rate limits, and any other operational constraints.

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 two compact sentences with no wasted words. The resource and return contents are front-loaded, and the cost note is brief and relevant.

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 simple one-parameter lookup with a fully described schema and no output schema, the description provides adequate context by naming the return categories (markets, products, ratings). It could say more about response structure or pagination, but the core invocation information is present.

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 description coverage is 100%, and the single vendor parameter is already fully documented with an example in the schema. The description repeats 'alias or URL' but adds no additional syntax, 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?

The description states a specific verb and resource: get a Gartner Peer Insights vendor profile by alias or URL, returning markets, products, and ratings. It clearly differentiates a vendor lookup from sibling product and market lookups, though it does not explicitly name the alternative sibling tools.

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 description gives no explicit when-to-use or when-not-to-use guidance compared with alternatives like run_gartner_product or run_gartner_market. It implies usage by naming the resource, but does not help an agent choose between this and the other Gartner tools.

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