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

Beyond simple functional requirements, the description dictates the tool's sorting behavior ('newest first') and its visibility behavior based on user roles and parameters. This provides essential behavioral context for an AI agent.

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 definition is highly concise, using three sentences that are front-loaded with the most vital information: the resource, the sorting order, and the visibility rules.

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?

The description successfully captures the complex visibility and filtering rules of the tool, which would be impossible to deduce purely from the minimal input schema and lack of annotations. It is a complete guide for calling this specific function.

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 0% schema description coverage, the description is critical. It explicitly explains the semantic difference of the optional 'shop_id' parameter, stating that omitting it defaults to showing all transfers related to the caller.

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 clearly identifies the resource being managed: 'Hand-offs of a shop'. It explains that these are 'Hand-offs of a shop,' which provides necessary context and distinguishes the operation from general shop management tools.

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?

This section provides extremely specific usage guidelines based on the executing agent's role ('owner' vs. 'worker') and the explicit presence or absence of the shop_id parameter. It tells the agent exactly when it is safe and appropriate to use the tool.

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