customers

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 hints at returning a 'verifiable store' but does not explain behavior, side effects, or prerequisites. The mention of 'proof' and 'absences' is unclear.

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 short but cryptic. Conciseness requires clarity; here it sacrifices understandability for brevity. The two sentences are ambiguous and fail to communicate effectively.

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 description is incomplete. With only one parameter and no output schema, the description should explain what 'features' and 'conspicuous absences' mean, and what the tool returns. It leaves many unanswered questions.

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 coverage is 0% (no description in schema for parameter 'merchant'). The description adds minimal meaning: 'Pass merchant for its verifiable store.' It implies merchant is an identifier but lacks type, format, or example.

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 is cryptic and vague. It mentions 'named merchants used as proof, mapped to features + conspicuous absences' without a clear verb or resource. It does not clearly state what the tool does.

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?

No guidance on when to use this tool versus its siblings. The description does not differentiate from other tools like 'deprecations', 'easter', 'get', etc.

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