search_stock_locations

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

The description discloses nothing about behavior beyond the name. Annotations show readOnlyHint=false, but the description does not clarify whether the tool modifies data, how results are paginated, or what the output structure is. With no added context, an agent cannot anticipate side effects or return formats.

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?

The description is only a single phrase, which is concise but under-specified. It provides no meaningful information beyond what the name already conveys, making it more of a lack of content than an efficiently structured description.

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, no explanation of pagination or filtering, and a vague body parameter, this description is entirely inadequate for an agent to understand how to construct a valid request or interpret the response. The presence of annotations does not compensate for the complete lack of contextual detail.

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 the schema itself documents all parameters. However, the body parameter is described only as 'Request body as defined by the bexio API', which is vague and does not explain its structure. Since the schema carries the burden, a baseline of 3 is appropriate.

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 'Search stock locations' is a direct restatement of the tool name, providing no additional detail about what the search does or what makes it distinct from the sibling 'list_stock_locations'. It is essentially a tautology rather than a clear explanation of the tool's specific purpose.

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 guidance on when to use this tool versus alternatives like 'list_stock_locations' or 'search_stock_areas'. No context is provided about typical use cases or situations where this search is appropriate.

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