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 does mention the output contents (badge tier, trust score, dates, SVG URL), which is helpful, but it does not explicitly state that the operation is read-only, lacks error behavior, or note any access considerations. This is partial transparency but not comprehensive.

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 well-structured: a one-sentence purpose, a bullet-like list of returns, and a single arg line. It is front-loaded with the core action and avoids filler, though the 'Args:' section could be formatted more cleanly.

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 simple getter with one parameter and an existing output schema, the description covers the essentials: what it does, what it returns, and what to pass. Still, it omits any mention of when to prefer this over the many similar sibling tools, and the absence of annotations leaves behavioral context incomplete.

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. The line 'did: The DID of the agent to check' provides a basic meaning for the lone parameter, which is more than the schema gives. However, it does not elaborate on format, validation, or examples, leaving room for ambiguity.

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') and resource ('Verified by MolTrust badge status'), with concrete return fields listed. However, it does not differentiate from the similarly named sibling mt_check_badge, so full 5 for sibling distinction is not earned.

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 given on when to use this tool versus alternatives like mt_check_badge, mt_issue_badge, or moltrust_verify. There are no usage conditions, exclusions, or references to sibling tools, so an agent is left to guess which one fits the scenario.

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