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

No annotations are present, so the description carries the behavioral disclosure burden. It states the output shape (yes/no with tier and expiry), which is helpful, but does not explicitly mention whether the operation is read-only, has side effects, or what the 'tier' and 'expiry' semantics mean. 'Quick check' implies non-mutating but this is not explicit.

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 very concise, front-loads the purpose in the first sentence, includes the return type, and lists the argument with a brief explanation. No unnecessary words or repeated schema information.

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 one-parameter tool with an output schema, the description covers the core purpose, parameter, and return type. It does not discuss errors or prerequisites, but the low complexity and presence of an output schema make this acceptable. The main gap is usage guidance, which is scored separately.

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 explain the parameter. It provides a one-line explanation ('The DID of the agent to check') which adds meaning beyond the schema's bare title, but does not include format, examples, or constraints. This is minimal but adequate for a single, self-explanatory parameter.

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 verb ('check') and resource ('badge-verified by MolTrust'), and mentions the return type (yes/no with tier and expiry). It is easy to understand, though it does not explicitly distinguish itself from the many sibling verification tools like mt_get_badge or moltproof_verify.

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 moltguard_credential_verify, moltrust_verify, or mt_get_badge. The description implies a quick badge check but gives no exclusions or selection criteria.

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