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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only operation via 'Get' and lists returned content, but does not explicitly state that it has no side effects, nor does it mention error behavior or authentication requirements. For a simple get, this is adequate but not rich.

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 filler. It immediately states the action and key content, making it easy for an agent to parse quickly. Every word contributes value.

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?

Given there is no output schema, the description does a good job of hinting at the response contents (cashback tiers, coupons, categories). However, 'full details' is somewhat vague and could be more explicit about what else is included. Still, it is sufficiently complete for a simple single-store retrieval 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?

The schema already documents store_id as 'Store ID' (100% coverage). The description adds minor context by tying the parameter to 'a specific store', but it does not explain format or any special semantics beyond what the schema provides. Baseline 3 is appropriate.

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 a specific verb ('Get') and resource ('full details for a specific store'), and enumerates the content (cashback tiers, active coupons, categories), which distinguishes it from sibling tools like get_deals or search_stores. An agent can immediately understand what this tool does and how it differs from its neighbors.

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 clear context—it is for retrieving comprehensive store information—but does not explicitly mention when not to use it or name alternative tools. It implies usage ('when you need full store details'), which is sufficient given the sibling list, but lacks explicit exclusions.

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