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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds value by naming the concrete fields returned (id, code, name, address, phone) and the underlying endpoint GET /stores, giving an agent a picture of the response shape despite no output schema. It does not discuss pagination behavior, which the schema covers instead.

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?

Three short sentences, front-loaded with the core verb and resource, followed by returned fields and the practical downstream use. "GET /stores" is marginally low-value but cheaply signals the endpoint. No filler or repetition.

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?

With no output schema, the description compensates by listing the returned fields, which is the main thing an agent needs. Pagination, sorting and sparse fieldsets are handled entirely by the 100%-covered input schema, and read-only safety is carried by annotations, so nothing critical is missing; only explicit sibling differentiation would make it fully complete.

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 page, sort, limit and fields are all fully documented in the schema including defaults, ranges and examples. The description adds nothing about parameters beyond the implicit point that returned fields include the listed attributes. Baseline 3 applies when the schema does the heavy lifting.

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 ("List the stores (shops) of the Smaregi contract") and enumerates the returned fields, so an agent knows exactly what comes back. It does not distinguish itself from the sibling smaregi_get_store, which likely fetches a single store, so the list-vs-single contrast is left implicit.

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?

"Use the ids to filter stock and transactions" gives a useful downstream purpose, implying when this tool is a prerequisite for stock/transaction calls. However it offers no explicit when-not guidance and no mention of when to prefer smaregi_get_store over this list, so usage remains implied rather than stated.

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