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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds useful behavior the annotations do not: the list is scoped to the caller's organization and supports status/visibility filtering with cursor pagination via starting_after. It omits default page size, ordering, and what happens when starting_after is exhausted.

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 compact sentences, front-loaded with what the tool returns and followed by how to use and narrow it. Every clause carries information; only the slightly clipped phrasing of the field list ('with status, visibility, radius and activation') is a minor readability cost.

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 zero-required-parameter list tool with no output schema, the description is adequately complete: it names the returned fields, the filters, and the pagination mechanism. It does not define radius/activation semantics, default limit, or result ordering, which an agent would need to page or interpret results confidently.

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 carry the load, and it only explains three of five parameters (status, visibility, starting_after as a pagination cursor). The limit and robomart_version parameters are left entirely to the schema, and the enum values themselves are already defined in the schema, so no extra meaning is added for those filters.

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 the resource and scope precisely: 'Stores this organization owns', which distinguishes it from the org-external implication of the sibling find_stores. It also enumerates returned fields (status, visibility, radius, activation), making the tool's output purpose concrete. It stops short of explicitly naming the sibling it is not, so it lands at 4 rather than 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?

It gives downstream guidance ('Use the store id to check coverage and book') and names the two filter axes, which implies the use case of narrowing a store list. However, it never says when to prefer list_stores over find_stores, which is the obvious sibling ambiguity. Usage is implied rather than resolved.

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