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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false, but the description adds genuinely new context: a $1 cost, a signed receipt as the output artifact, prerequisites ('checkout caller and verified fixed-order session'), and the explicit statement that no endpoint is fetched or tested. That is meaningful disclosure beyond the 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?

The purpose and return value are front-loaded, which is good, but the middle sentences about the MCP caller and the x402 rail's 'introductory quote policy' are jargon-heavy and their relevance to invoking the tool is unclear, costing the agent parse effort.

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?

With an output schema present, return-value explanation is not required, but for an 8-parameter tool with nested objects and 0% schema coverage, the description leaves too much unspecified. An agent cannot confidently populate manifest, policy, or the payment/session fields from this text alone.

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 description coverage is 0% across 8 parameters, including nested objects (manifest, policy, sample_inputs), and the description explains none of them. It only indirectly alludes to a session requirement, leaving agent_id, manifest, policy, and payment_ref semantics entirely undocumented.

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 gives a concrete verb+resource ('Run a $1 static Security Preflight') and the return artifact ('signed receipt'), plus a scope qualifier ('No deployed endpoint is fetched or tested') that separates it from a live scan. It does not name any sibling tool, so the differentiation from scan_source/screen_injection is left implicit.

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?

It implies usage context by stating what does not happen (no endpoint fetched) and that importing the receipt is a separate action, which hints at a static-assessment use case. However, there is no explicit when-to-use/when-not vs alternatives, and the mention of MCP vs x402 rails reads as payment plumbing rather than selection guidance.

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