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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context they don't carry: stateless edge call, 32 KB payload cap, 60 RPM rate limit, demo mode or L402 payment of 25 sats, and an HTTP 400 failure mode on invalid input. That is exactly the operational detail an agent needs before invoking.

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?

Purpose and routing come first, with operational constraints trailing — good front-loading and no filler sentences. The final sentence is a dense run-on packing rate limits, payment, and error codes together, which slightly hurts scanability.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. Combined with the stated rate limits, size cap, payment path, and default framework, an agent has everything needed to call this correctly.

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%, so baseline is 3; the description earns extra by disclosing the default value of 'analysis_framework' ('feature_and_pricing_matrix'), which the enum schema does not state. It also names the required parameter, though max_competitors is left entirely to 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?

States a specific verb (compiles) plus the concrete artifacts produced: comparison matrices, pricing tiers, feature coverage, and moat evaluations. It explicitly contrasts itself with compile_research_dossier, so an agent can distinguish the two without opening either schema.

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?

Gives three concrete triggering scenarios (market landscape analysis, pricing parity, competitive diligence) and names the alternative tool for the adjacent task (narrative research briefs). Both the when-to-use and when-not-to-use sides are covered.

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