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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is clear. The description adds the air-gapped aspect, which implies privacy and offline processing, but does not disclose whether results are cached, if there are rate limits, or the nature of the 402 payment flow beyond the schema.

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 a single, concise sentence that is front-loaded with the core purpose ('AI analysis' and 'air-gapped model'). It is efficiently worded with no fluff, though it could be slightly more specific without sacrificing brevity.

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?

Given the tool's moderate complexity (2 params, output schema present, annotations cover safety), the description is mostly sufficient. However, it omits details like whether output is structured as JSON, expected latency, or if there are content restrictions, which an agent might need for a paid call.

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 schema has 100% coverage with detailed descriptions for both prompt and paymentProof, so the description adds minimal value. It does not explain the relationship between paymentProof and the 402 quote, but the schema already states that omitting it yields a price quote. Baseline 3 is appropriate given high coverage.

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 identifies the tool as performing AI analysis via an air-gapped model, which is specific enough to distinguish it from generic 'analyze' tools. However, it does not mention what kind of analysis it supports (e.g., research, code review), leaving some ambiguity compared to siblings like analysis.summarize_clean.

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 implies use for research questions or task instructions, and the paymentProof parameter suggests a paid usage model, but it does not explicitly state when to use this tool versus alternatives like analysis.summarize_clean or security.audit_agent_code. No exclusions or alternative recommendations are provided.

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