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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned field set and the GET endpoint, but says nothing about result volume, ordering, or what an empty result means; the next_query argument-ignoring rule is already in the schema, so it earns no extra credit here.

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 purpose, then usage, then pagination. Every clause carries information and nothing is repeated from the schema verbatim.

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 five-parameter read-only list tool with full schema coverage and no output schema, the description covers purpose, record contents, pagination and downstream use of ids. A brief note on what the response envelope looks like or on default ordering would close the remaining gap.

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 name, query, active, limit and next_query are fully documented in the schema. The description adds no filtering guidance (e.g., name vs. query, which to use for exact vs. fuzzy matching), so it only meets the baseline for a fully-described schema.

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?

Specific verb+resource ("List branches") with the useful clarification that branches are shops and a statement of what each record contains (number, name, address). It does not name a sibling tool explicitly, but the pointer to using returned ids for transactions/stock/prices implicitly separates it from the list_* 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?

"Use the ids to filter transactions, stock and prices" gives a concrete reason to call this before the transaction/stock/price tools, and "Page with next_query" tells the agent how to continue. There is no explicit when-not or named alternative, so it falls short of a 5.

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