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

The description says 'air-gapped AI,' which implies isolation from external networks, while the annotation openWorldHint=true suggests the tool may interact with the outside world. This is a direct contradiction and makes the description actively misleading. No additional behavioral context such as payment/quote behavior or uncensored output is disclosed either.

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 extremely short and front-loaded, which is economical. However, it is more of a tagline than a structured definition, and it omits essential behavioral context while also creating an annotation contradiction. It is concise but under-specified.

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?

Despite having an output schema and annotations, the description fails to explain the payment requirement, the 402 quote behavior implied by the schema, the scope of acceptable exploit research, or how this tool relates to the security siblings. The sparse description is not complete enough for an agent to use this tool confidently.

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?

Both parameters (prompt and paymentProof) are fully described in the input schema, so the schema carries the documentation burden. The description adds no parameter-level meaning, which is acceptable at the baseline of 3 given 100% schema description 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 indicates the tool performs exploit research via an air-gapped AI, and the title adds the 'uncensored' qualifier. However, it reads as a noun phrase rather than a full statement of behavior and does not explicitly differentiate itself from related siblings such as security.hack_autopsy or analysis.offline_ai.

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 provides no guidance on when to use this tool, what prerequisites exist, or how it compares to alternatives. The paymentProof parameter in the schema implies a payment flow, but the description itself gives the agent no routing or selection context.

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