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

With no annotations provided, the description must carry the behavioral transparency burden. It does state that the tool returns service description, supported segments, and API endpoints, making it clear this is an informational read. It does not explicitly confirm the absence of side effects, mention authentication requirements, or describe rate limits, but for a zero-parameter info endpoint this is a reasonable level of disclosure.

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?

The description is two concise sentences with no filler. The primary purpose is front-loaded in the first sentence, and the second sentence adds exactly the detail needed about the return content.

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?

For a zero-parameter discovery tool with an output schema present, the description is complete. It tells the agent what the tool does, what it returns, and which domain it belongs to, so the agent can decide to call it and know what to expect.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to add parameter meaning because there are no inputs to document and the schema already covers everything.

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?

The description uses a specific verb and resource: 'Get MT Travel service information and available endpoints.' It further clarifies the scope by listing what is returned: service description, supported segments, and API endpoints. This clearly distinguishes it from action-oriented siblings like mt_travel_issue_vc and mt_travel_verify.

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?

The description implies this is a service-discovery tool that should be called to obtain service information and endpoint details before interacting with the MT Travel booking trust protocol. However, it does not explicitly state when to use it versus alternative tools, nor does it mention exclusions or prerequisites.

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