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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions immutable hashes and a cost of 0.004 USDC, which is useful, but it does not state side effects such as whether the tool performs network fetches, writes evidence, verifies hashes, or what happens on failure. This is minimal transparency for an on-chain evidence operation.

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 compact and front-loaded, with no filler words. However, it is terse to the point of ambiguity, and the cost annotation is placed awkwardly after a semicolon rather than integrated into a clear behavioral explanation.

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 two parameters, no output schema, and no annotations, this single cryptic sentence is completely inadequate for an agent to select and invoke the tool correctly. It omits the action performed, the meaning of subject, how source_urls are used, what the evidence output looks like, and when this tool should be preferred over any sibling evidence tool.

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 the description must compensate for both source_urls and subject. The phrase 'Public explorer or RPC response evidence' hints that source_urls should point to public explorer or RPC endpoints, but it never mentions the subject parameter or explains its role. The description adds only weak contextual meaning beyond the schema's bare parameter list.

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 identifies the resource as 'Public explorer or RPC response evidence with immutable hashes', which gives some clue that this tool deals with on-chain evidence and hashes. However, it lacks an explicit verb or clear action statement, so an agent cannot tell whether this tool creates, verifies, or fetches evidence. It also does not clearly distinguish itself from the many sibling evidence tools beyond the 'public explorer or RPC' phrase.

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?

There is no explicit guidance about when to use this tool versus siblings such as fetch_evidence, delivery_evidence, or domain_ownership_evidence. The phrase 'Public explorer or RPC response evidence' implies a use case, but no conditions, 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.