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

readOnlyHint=true already tells the agent this is a safe, side-effect-free read, so the annotation does much of the work. The description adds value by listing what the response contains (version, endpoints, credential schema), but says nothing about authentication requirements, rate limits, or whether the endpoint set is environment-specific.

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 short sentences with the resource stated first and the return contents second, so it is front-loaded and waste-free. The awkward line breaks and the vague trailing phrase 'verification details' cost it a point but not readability.

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 no-parameter read-only metadata call with an output schema present, the description covers everything an agent needs to decide to call it: what it returns and that it is informational. The only real gap is the absence of guidance on when to prefer it over the sibling verify/issue_vc tools.

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 takes zero parameters, so per the baseline there is nothing for the description to disambiguate. Schema coverage is 100% and the empty object schema is unambiguous.

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?

Uses a specific verb and resource ('Get MT Shopping API information') and enumerates the returned contents: version, supported endpoints, BuyerAgentCredential schema, verification details. It does not explicitly distinguish itself from siblings like mt_shopping_verify or mt_shopping_issue_vc, though 'info' vs 'verify'/'issue_vc' carries some natural differentiation.

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?

Usage is implied rather than stated: an agent can infer this is a discovery/metadata call to make before invoking mt_shopping_verify or mt_shopping_issue_vc. There is no explicit 'use this when...' statement, no mention of prerequisites, and no named alternative.

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