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

There are no annotations, so the description carries the full burden. It does disclose output format (score and grade) and a notable behavioral trait—cost of $0.25 USDC on Base via x402—which is useful. However, it omits whether the tool is read-only, how inputs are handled, and any permission or rate-limit considerations, leaving significant gaps for an unannotated tool.

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 core purpose and output, followed by cost and payment details. Every sentence adds value with no filler.

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 no annotations, no output schema, and 0% schema coverage, the description must do more. It adequately covers purpose, output format, and pricing, but it is incomplete on parameter usage and operational behavior, leaving the agent without enough information to call it correctly in all cases.

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%, and the description never mentions the three parameters (email, handle, fullName). The listed vectors imply identity-based inputs, but there is no explanation of which identifier to use, whether combinations are allowed, or what happens if none are supplied (all are optional).

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 states a specific resource and output: a multi-vector OPSEC exposure score (0–100, grade A–F) covering four named data sources. It is clear what the tool produces, but it does not explicitly differentiate itself from siblings like full-privacy-sweep or threat-scan, leaving the agent to infer the distinction.

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 explains what the tool is but gives no guidance on when to choose it over alternatives, no prerequisites, and no conditions for use. The only practical note is the cost, which is not usage guidance.

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