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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds real value beyond them: it lists the returned attributes (compensating for the missing output schema) and supplies the underlying endpoint GET /api/Inventory/GetStockLocations, plus the id-linking contract. It does not mention pagination, auth requirements, or whether inactive locations are included.

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?

One compact sentence front-loads the purpose, followed by the field enumeration and the id-reuse note; the endpoint reference is the only mildly technical extra and it aids API mapping. Nothing is padded or restated from the title.

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 carries the burden of describing return content, and it does so by naming id, name, address and fulfilment-centre status. It is complete enough to invoke and consume correctly, though it is silent on result ordering, pagination, and whether disabled locations appear.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly indicates a non-parameterized call and adds the meaningful clarification that returned ids are consumed as location_id elsewhere.

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 stock locations') and immediately disambiguates the domain term with parenthetical synonyms ('warehouses, fulfilment centres'). It also enumerates the returned fields (id, name, address, fulfilment-centre flag), so an agent knows exactly what this call yields, and no sibling is close enough to be confused with it.

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?

Gives explicit downstream usage guidance: 'Use the ids as location_id in other tools,' which tells the agent why and when to call this relative to the rest of the surface. There is no true alternative tool to exclude, so the absence of when-not guidance is a minor gap rather than a real omission.

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