MolTrust

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

Discloses return values (service description, segments, endpoints) but lacks info on auth requirements, caching, or rate limits since no annotations exist.

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?

Compact three-sentence structure with clear front-loading; no redundant 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?

Mentions 'booking trust protocol' for domain context but omits workflow relationship to mt_travel_issue_vc/mt_travel_verify; adequate for simple info tool.

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 parameters present, meeting baseline requirement.

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 ('Get') and resource ('service information and available endpoints'), distinguishes from action-oriented siblings like mt_travel_issue_vc and mt_travel_verify by specifying it's for retrieval/discovery.

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?

Provides no guidance on when to use this vs alternatives or prerequisites (e.g., call this before booking).

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