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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only lists what the tool returns and does not state whether it is read-only, whether it requires authentication, or what happens with invalid addresses. It does not contradict any annotations (none exist), but it fails to communicate side-effect or constraint information beyond the obvious 'get' action.

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 succinct and well-structured: a single purpose sentence, a bullet-like list of return contents, and a clear Args section. It is front-loaded with the primary action and avoids unnecessary verbosity. Every sentence adds value.

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 single-parameter tool with no annotations and an output schema, the description covers the essential invocation details: what the tool does, what it returns, and the parameter format. It does not address potential edge cases or prerequisites (e.g., wallet must be registered), but these are not critical for basic usage. The description is largely complete, missing only deeper context like when to prefer it over simpler siblings.

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 only defines 'address' as a string with no description (0% coverage). The description compensates by specifying 'Base (EVM) wallet address (0x...)' in the Args section, adding format and chain context. This is valuable and makes the parameter actionable, though it could add more validation rules or examples.

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 states a specific action ('Get a detailed agent trust report') and the resource (Base wallet address). It distinguishes itself from siblings like moltguard_score by emphasizing 'detail' and listing specific return components (scoring breakdown, wallet history, ERC-8004, DID cross-reference, Sybil indicators), making its purpose unambiguous.

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 versus alternatives such as moltguard_score or moltguard_sybil. It does not mention conditions, exclusions, or recommend this tool for certain scenarios. There is no 'use this when' or 'for a simple score use...' context, leaving the agent to infer selection.

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