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

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is fully covered by structured data. The description adds scope value by noting it only covers configured contracts and omits native traffic, but says nothing about freshness/caching, who signs the report, or expected failure when nothing is configured.

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, front-loaded with the artifact returned, followed immediately by the negative scope. No filler and nothing repeated from the schema or annotations.

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 zero-parameter, no-output-schema tool, the agent cannot learn what fields the SecurityReportV1 contains, whether it answers the question at hand, or how to verify it (sibling verify_attestation exists). The description is accurate but thin on what the caller actually receives.

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?

Zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the mention of chain_id=1 correctly signals that the chain is fixed rather than configurable.

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?

Specific verb + resource ('Return the current signed SecurityReportV1') with an explicit scope (configured Fetch/ASI contracts on Ethereum, chain_id=1). It distinguishes itself from the network_state_attestation siblings by naming the exact artifact type, though a reader still needs domain knowledge of what SecurityReportV1 is.

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 exclusion 'does not evaluate native fetchhub-4 traffic' implies that native traffic queries belong elsewhere, but no sibling is named and no positive trigger ('use this when you need an auditor-verifiable snapshot') is given. Usage is inferable rather than stated.

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