MolTrust

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

Discloses Ed25519 crypto method and conditional payload return, but omits failure behavior for invalid signatures (exception vs. null vs. false) and lacks auth/rate limit details.

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 tight structure with no filler; front-loaded with specific action verb and crypto detail, followed by Args annotation.

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 single-parameter verification tool given output schema exists, but missing error handling semantics and validity criteria expected for cryptographic verification.

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?

Effectively compensates for 0% schema description coverage by specifying the JWS parameter as 'compact serialization string from a MoltGuard credential' in the Args section.

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 it verifies Ed25519 JWS signatures for MoltGuard credentials, distinguishing from the 'issue' sibling and other verification tools via specific domain mention.

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 on when to use versus moltguard_credential_issue or other verification tools in the moltrust/mt families.

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