hyperscaler_deals

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

Adds refresh rate (10-min), data source (dchub news pipeline), and processing details (regex extraction). Annotation readOnlyHint is consistent; no contradiction.

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?

Packed with useful information, front-loaded with purpose. Slightly long but every sentence adds value; no wasted words.

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?

Covers data source, refresh, typical magnitude, classification, and exclusions. Missing explicit return format, but implications are clear. Adequate for a simple list tool.

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?

Only parameter 'limit' has no schema description (0% coverage). Description does not explain its purpose or effect. With no schema description, the description should compensate but does not.

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 it's a 'live feed' tracking hyperscaler AI deals, listing specific actors and deal types. It distinguishes from siblings like list_transactions and deal_autopsy.

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 'Do NOT use for' section provides clear alternatives (list_transactions for historical M&A, deal_autopsy for single-deal teardown). Tells when to use (tracking AI capex events).

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