list_stock_transfers

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost none of it. It never states that this is a read-only operation, nor does it mention pagination behavior despite skip/count/includeCount existing, nor does it describe ordering or result shape.

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?

A single short sentence with the resource and scoping qualified up front and no filler. It is efficient, though the brevity comes at the cost of substance rather than being purely economical.

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 12-parameter, zero-required, no-output-schema, no-annotation list tool, one sentence is insufficient. The agent is left without pagination, filtering, sorting, or safety context for an operation whose behavior is entirely undescribed.

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?

With 12 parameters and only 58% schema description coverage, the description must compensate, but it adds nothing beyond the phrase 'between locations' loosely pointing at fromLocationId/toLocationId. Unlabeled parameters such as skip, count, include, transferDateFrom and transferDateTo remain undocumented in both schema and description.

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 pair (search/list) and resource (stock transfers), plus a scope qualifier (between locations) that tells the agent this returns transfer records. It does not explicitly differentiate itself from get_stock_transfer, upsert_stock_transfer, or set_stock_transfer, so a reader must infer the list-vs-single-vs-mutate split.

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?

There is no when-to-use guidance: nothing says to use this for browsing/filtering transfers versus get_stock_transfer for one record or upsert/set_stock_transfer for writes. The word 'Search' loosely implies filtering, but no conditions or alternatives are stated.

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