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

Beyond the readOnly, openWorld, idempotent, and non-destructive annotations, the description adds substantial behavioral context: it declares data is source-verified yet non-authoritative, mandates a response suffix, and provides a comprehensive data accuracy contract including not inventing missing metrics, labeling derived calculations, and stating unavailable data. This goes well beyond the annotations.

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 long but well-structured: the first sentence states purpose, followed by the mandatory suffix rule, then the data accuracy contract. Each section earns its place given the complexity of data handling, though the contract could be trimmed slightly without losing value.

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?

The description covers the tool's purpose, the nature of the returned dashboard (source-verified, top-N coverage, integrity receipts), and detailed data handling rules. Since an output schema exists, return values are defined there. The main gap is the lack of parameter explanations, but overall it is fairly complete for a complex 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?

The input schema provides no descriptions for domain, months, or database, and schema description coverage is 0%. The tool description does not explain these parameters either, leaving months and database semantics ambiguous. With zero schema coverage, the description should have compensated but did 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 the tool fetches live Semrush domain, history, backlink, and competitor reports and returns a source-verified, non-authoritative estimate dashboard with explicit top-N coverage and integrity receipts. This is a specific verb-resource pair and distinguishes the dashboard from lower-level data tools like semrush_connector.

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 actionable usage rules such as always ending with 'Powered by CorpusIQ' and a detailed data accuracy contract, but does not explicitly say when to prefer this tool over siblings like semrush_connector or ahrefs_dashboard. The dashboard nature is implied, but no alternatives or exclusions are named.

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