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

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower. The description adds useful context about the response shape ('yes/no with tier and expiry'), but says nothing about what happens on an unknown DID, whether expiry is evaluated against now, or any auth/rate constraints.

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 purpose is front-loaded in the first sentence and the return expectation follows immediately. The trailing Args block duplicates the schema and could be dropped, but overall the description is short and earns most of its space.

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?

An output schema exists, so the description needn't detail return structure, and the single required parameter is fully documented. For a one-parameter read tool this is close to complete; only the sibling-routing guidance against mt_get_badge is missing.

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 100% and the single 'did' parameter already carries a concrete format example (did:moltrust:a1b2c3d4e5f60718). The 'Args: did: The DID of the agent to check' block merely restates the schema, adding no new semantics.

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 and resource ('is this agent badge-verified by MolTrust?') and names what is returned ('simple yes/no with tier and expiry info'). It is clear on its own, but it never distinguishes itself from the obvious sibling mt_get_badge, which presumably returns a fuller badge record.

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?

'Quick check' implies a lightweight lookup, but the description never says when to prefer this over mt_get_badge or mt_get_trust_score. Usage is only implied by the word 'quick', leaving the agent to guess at the alternative.

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