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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds genuinely new behavioral context: the two-tier ranking semantics, that PRIORITY domains are research candidates 'without proof of live links or publisher awareness', noise filtering, and the exact cost model (one gap job + one backlinks call per enriched target). This is exactly the kind of cost/side-effect disclosure that goes beyond structured fields.

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?

Front-loaded with the one-line framing ('The warm-outreach play'), then dense but purposeful detail. Every clause adds information, though the ranking definitions make it longer than strictly minimal.

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 multi-tier ranking tool with an output schema present, the description covers the ranking logic, the caveat on unverified targets, noise filtering, and cost. An agent has everything needed to invoke it correctly, and return format is handled by the output schema.

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 the baseline is 3, but the description adds meaning: 'top N priority targets are scored by authority' explains enrich_top, 'Platform/CDN noise is filtered' explains include_platforms, and 'Use 2-3 competitors' adds guidance on competitor_domains beyond the schema's 2-5 range.

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+resource: runs a gap analysis and ranks results into PRIORITY/SECONDARY outreach targets. It distinguishes itself from the sibling gap_analysis by framing the output as an outreach play with scoring, so an agent can tell the two apart without opening a 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 clear context ('the warm-outreach play') and a concrete recommendation ('Use 2-3 competitors'), plus a cost caveat. It does not explicitly say when to prefer this over gap_analysis or backlinks, so it lacks the exclusion/routing language that would earn a 5.

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