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

With no annotations, the description carries the full burden of behavioral disclosure. It does not say whether reports are public, require authorization, are rate-limited, reversible, or what happens after submission — all critical for a mutation-style tool interacting with a community system.

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?

A single efficient sentence that front-loads the action and resource. It is appropriately sized, though its brevity comes at the cost of missing behavioral and parameter detail.

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 tool with three parameters, no annotations, no output schema, and 0% schema description coverage, the description is far too thin. It omits prerequisites, side effects, expected response, and parameter semantics, leaving an agent with insufficient information to invoke it correctly.

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%, so all three parameters (address, chain, reason) are undocumented. The description does not add any meaning to these parameters, such as address format expectations, valid chain values, or whether reason is optional context.

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 verb ('report') and resource ('suspected scam address') and names the target system ('PathGuard's community reporting system'). It distinguishes the tool from siblings like check_transaction or preflight_transaction, which perform checks rather than reports, though the differentiation is implicit rather than explicit.

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?

No guidance is provided on when to use this tool versus alternatives such as check_transaction or preflight_transaction. An agent cannot infer whether reporting is a precursor to or substitute for those checks, leaving usage conditions entirely unstated.

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