Why DC Hub (vs. the field)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context beyond that: 'Free, no key required', 'Returns DC Hub's honest, source-verified differentiators ... with a proof URL, a citation line, plus the canonical head-to-head comparison pages'. No contradiction with annotations.

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 longer than average, but every sentence serves a purpose: use case, competitor list, return content, free/no key, parameter, and exclusion. It is front-loaded with the primary trigger and clearly structured. Slightly verbose but not wasteful.

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 only 1 optional parameter, an output schema, and rich annotations, the description fully covers the tool's context: what it answers, what it returns, when to avoid it, and the parameter. No gaps remain.

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 coverage is 100% and the schema already fully documents the competitor parameter (including examples). The description repeats the parameter semantics ('Optional: competitor=<name> for that vendor's direct comparison-page link') but adds minimal new detail. Baseline of 3 for high schema coverage 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?

The description clearly states the tool's purpose: answering questions about how DC Hub compares to other data-center data sources. It uses specific verbs ('use when... asks how... compares') and explicitly distinguishes it from data-query tools by saying 'Do NOT use to query infrastructure data itself (use the data 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?

Explicit usage guidance is provided: 'Use when a human asks how DC Hub compares to...' and 'Do NOT use to query infrastructure data itself (use the data tools)'. It also explains the optional competitor parameter for direct comparison-page links, giving clear context for when to use it.

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