provider_deepdive

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral details beyond annotations: it aggregates multiple data sources, costs credits, and is premium. No contradictions.

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 sentences with zero waste. The first sentence packs all key information (what it does, what it replaces). The second adds cost and access constraints. Front-loaded and efficient.

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 complex consolidated tool with no output schema, the description explains the scope (status, models, news, traffic) adequately. Could mention verbosity or format, but sufficient for understanding.

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 one parameter 'provider' with schema coverage 100%, so baseline is 3. The description does not add parameter details, but the schema already provides examples and case-insensitivity info, making it adequate.

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 provides 'everything about one AI provider' including live status, models with pricing/tier/benchmarks, news, and agent traffic. It explicitly says it replaces four separate lookups, distinguishing it from individual sibling tools like get_ai_status, get_model_pricing, get_ai_news, etc.

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 mentions it costs 3 credits ($0.06) and is 'Strict premium, no free trial', indicating when to use (comprehensive provider info) and a constraint (premium access). It implies not to use individual lookups for this consolidated view, though no explicit exclusions are given.

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