MolTrust

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

Discloses specific verification aspects (revocation check, on-chain anchor status, human oversight, rights) and return value structure beyond what annotations provide.

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?

Well-structured with front-loaded purpose statement and clear Args section; no extraneous text.

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?

Sufficient for a single-parameter tool; acknowledges output schema existence by summarizing return content (provenance summary) without over-specifying.

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?

Args section compensates for 0% schema description coverage by specifying credential_id is a UUID referring to the music credential.

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?

Clearly states the specific action (verify) and resource (VerifiedMusicCredential by ID), though could sharper differentiate from mt_get_track_provenance which also returns provenance data.

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 explicit guidance on when to use this versus mt_issue_music_credential or mt_get_track_provenance; only describes internal behavior.

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