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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only restates that metadata is fetched; it does not mention auth requirements, permission scope, error behavior, rate limits, or return shape. The read-only nature is implied by 'Get' but not elaborated.

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 a single, front-loaded sentence with no wasted words. The resource and key input are stated immediately. It is appropriately sized for a simple lookup tool.

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?

The tool is low complexity, but there is no output schema and the description does not explain what 'metadata' contains or what auth behavior to expect. It is complete enough to invoke with the required merchantPubkey, but leaves gaps an agent may care about.

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?

Schema description coverage is 100%, so both merchantPubkey and bearerToken are already documented in the schema. The description mentions merchantPubkey but adds no format or usage detail beyond the schema. Baseline 3 is appropriate when the schema does the parameter documentation.

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 states a specific verb and resource: get metadata for a merchant. It also names the key input, merchantPubkey, making the operation clear. It does not explicitly differentiate itself from the sibling list_merchant_metadata, so it falls short of a 5.

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 does not state when to use this tool versus alternatives such as list_merchant_metadata or get_profile. There is no guidance on prerequisites, auth needs, or exclusions. The singular phrasing implies lookup for one merchant, but that is not explicit guidance.

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