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

No annotations are provided, so the description carries the full burden. It explicitly states that the tool 'Returns the MT Shopping service info including version, supported endpoints, BuyerAgentCredential schema, and verification details,' which discloses the core behavioral output. It does not mention side effects or auth requirements, but 'Get' and 'Returns' strongly imply a safe, read-only operation, making this adequately transparent for a 0-parameter info endpoint.

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 with no wasted words. The main purpose is front-loaded, and the second sentence adds useful specifics about the response contents without being verbose.

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 simple info tool with no parameters and an output schema present, the description is sufficiently complete. It states what the tool does and what the response includes, and the output schema covers the detailed return structure. No critical information for calling the tool correctly is missing.

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 and the input schema is empty, so the schema coverage is trivially 100%. The description correctly does not add parameter details, and the baseline for a no-parameter tool is 4.

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 clearly states the verb ('Get') and the resource ('MT Shopping API information'), and lists the included contents. It does not explicitly distinguish from sibling tools like mt_shopping_verify or mt_shopping_issue_vc, but the purpose is specific and unambiguous enough that an agent can tell this is the metadata/info endpoint.

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 provides no guidance on when to use this tool versus alternatives. It does not say 'use this before issuing credentials' or point to sibling tools for verification actions. The usage is only implied by the name and description, which is not explicit enough for a dimension that asks for when/when-not guidance.

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