MolTrust

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

Without annotations, description mentions return payload but omits explicit behavioral traits (read-only, safe, idempotent) that would help an agent understand it's a non-destructive discovery call.

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?

Two sentences, front-loaded with action, no redundancy—optimal length for a simple discovery endpoint.

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 low complexity; mentions specific schema (BuyerAgentCredential) to contextualize within shopping domain, and presence of output schema reduces need for detailed return value explanation.

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?

Zero-parameter tool; baseline score applies as no parameter explanation is needed.

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?

Clear verb-object structure ('Get MT Shopping API information') and specifies returned data (version, endpoints, schema), distinguishing it from sibling 'mt_shopping_issue_vc' and 'mt_shopping_verify' via the 'info' designation.

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 query this metadata endpoint versus using the functional shopping tools (issue/verify) or how it relates to 'mt_travel_info'.

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