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

With no annotations, the description carries the full behavioral burden. It usefully adds cost ('Flat 5 points per successful run') and lists the return fields, but it does not disclose whether the operation is read-only, what permissions are required, or any rate-limit behavior. It adds some value beyond structured fields but leaves key behavioral context uncovered.

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 sentences with zero waste: the first front-loads purpose, input method, and return scope; the second adds a key operational fact (cost). No filler or repetition.

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 single-entity lookup with one documented parameter and no output schema, the description covers purpose, input, return fields, and cost. The only gap is explicit routing guidance against its many siblings, which slightly limits completeness.

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%, so the single 'product' parameter is already documented with an example ('forcepoint-dlp'). The description adds no syntax or format details beyond what the schema provides, so the baseline of 3 applies.

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'), names the input method ('by alias or URL'), and lists the return scope ('vendor, ratings, and company profile'). This clearly distinguishes it from a search tool, but it does not explicitly name or contrast with any sibling tool (e.g., run_gartner_products_search or run_gartner_vendor).

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, nor does it name alternatives among the many sibling tools. The phrase 'by alias or URL' hints at how to invoke it, but there is no routing logic to help an agent pick this over run_gartner_products_search or run_gartner_vendor.

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