MolTrust

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

Discloses return format (yes/no with tier/expiry) but misses other behavioral traits like error handling when badge absent, rate limits, or read-only nature.

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?

Extremely concise with zero filler; front-loaded question format immediately communicates purpose before parameter details.

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?

Adequate for simple single-parameter tool; acknowledges output schema existence by summarizing return structure rather than detailing fields.

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?

Compensates for 0% schema coverage by defining 'did' as 'The DID of the agent to check', clarifying the parameter's semantic role.

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?

States specific action (check badge verification) and target (MolTrust agent badges), with 'Quick check' hinting at distinction from detailed retrieval tools like mt_get_badge.

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?

Implies usage context through 'Quick check' (simple yes/no needed), but lacks explicit when/when-not guidance or comparison to mt_get_badge alternative.

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