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

The description explicitly claims 'Idempotent: re-submitting for the same shopSlug within the pending window returns the existing requestId,' which directly contradicts the annotation idempotentHint: false. This is an annotation contradiction, so the score must be 1 even though the description does add useful auth and error details.

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 tightly focused paragraphs. The first front-loads the core action, workflow, and return value; the second delivers essential auth requirements and error behavior. No filler sentences.

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?

Without an output schema, the description correctly states the return value (requestId + PENDING) and explains the auth error path in detail. It omits parameter meanings and sibling routing, but the core operation is well covered for a simple two-parameter tool.

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 0%, so the description must compensate for the undocumented parameters. It only references shopSlug indirectly in the idempotency note and never explains its pattern or meaning; notes is not mentioned at all. The description fails to add meaningful parameter semantics.

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?

States a specific verb and resource: 'Submit a brand attestation request for a droplinked shop.' It also clarifies the workflow (operator review + approval triggers on-chain mint) and the return value (requestId + PENDING), making it clearly distinct from status-checking and verification siblings.

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 tool is for creating an attestation request while get_brand_attestation_status would be for checking status, but it never explicitly states when to use this tool versus alternatives. It provides context around auth tiers but not usage exclusions.

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