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

Beyond the read-only/idempotent annotations, the description discloses what the tool returns (proof URLs, citation lines, comparison pages), states that it is free and requires no key, and even surfaces a notable transparency detail about the DCGI index being withdrawn and restored. This gives the agent a clear model of the tool's behavior.

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 front-loaded with the primary use case and contains rich, decision-relevant detail. However, it is a long run-on sentence with deeply nested parentheticals, including exact dates and a long differentiator list, which makes parsing harder than necessary.

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?

Given the simple input schema, the rich annotations, and the presence of an output schema, the description covers everything an agent needs: when to use it, what it returns, the optional parameter's behavior, the free/no-key fact, and an explicit exclusion. No critical invocation context is missing.

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 only one optional parameter and the schema already describes it well with examples. The description essentially restates the same purpose ('Optional: competitor=<name> for that vendor's direct comparison-page link'), so it adds modest value but does not meaningfully exceed the schema.

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 use case: answering human questions about how DC Hub compares to other data-center data sources, with named competitors and example question phrasings. It clearly distinguishes itself from infrastructure data tools by explicitly 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?

The description gives explicit when-to-use guidance ('Use when a human asks how DC Hub compares...'), example question forms, and an explicit when-not-to-use exclusion with a pointer to alternative tools. It also explains the optional competitor parameter's behavioral effect.

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