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

Annotations already declare readOnlyHint/idempotent/openWorld=false; the description adds the important reassurance that 'this tool sends nothing by itself', resolving what an 'order' tool actually does. It also discloses the return payload (cleaned list + order_url), which the annotations cannot convey.

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 tight sentences: action, mechanics/return, then the key non-side-effect caveat. No filler and the most decision-relevant information (id source, no sending) is front-loaded.

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 3-parameter tool with no output schema, the description covers inputs, the return shape, and the non-destructive behavior. It does not mention failure modes such as an invalid or unknown grocery_id, which would be the last missing piece.

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 coverage is 100%, so baseline is 3, but the description adds meaning: grocery_id is a foreign key from find_groceries and items are normalized ('returns the cleaned list'), telling the agent input phrasing is flexible. It does not describe note handling or item-limit behavior.

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+resource (turn a shopping list into a ready order) and names the sibling find_groceries as the required id source. An agent can distinguish this from find_groceries or dukkani_for_shop_owners without opening any schema.

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?

Explicitly says the grocery_id must come from find_groceries, giving the correct upstream call order, and clarifies the customer completes the order elsewhere. It lacks an explicit 'do not use for X' exclusion, but the when-to-use context is unambiguous.

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