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

Annotations only declare destructiveHint=true and a title. The description adds genuine behavioral value by disclosing that the order starts as an estimate and that services must be added in the UI, but it omits auth/permission needs and does not clarify that all ten inputs are optional.

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?

Two short sentences front-load the action and the estimate nuance, with the API route appended as compact metadata. Nothing is padded, though the trailing 'Shopmonkey: POST /v3/order' is of marginal use to an agent.

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 ten-parameter creation tool with zero required fields, no output schema, and only a destructiveHint annotation, the description should indicate which fields are needed for a valid order and whether a partial payload succeeds. It covers the workflow hint but leaves the creation contract underspecified.

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 every parameter is already documented, including cross-references to shopmonkey_get_current_user and shopmonkey_list_workflow_statuses. The description adds no parameter-level meaning beyond the schema, so the 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?

States a specific verb and resource ('Open a new work order') and scopes it ('for a customer and vehicle'), plus a useful nuance that it begins as an estimate. It implicitly separates itself from create_appointment/create_customer siblings but never names them.

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?

The line 'Add services in the Shopmonkey UI' conveys a real constraint (services cannot be added via this call) and implies workflow context. However, there is no explicit when-to-use guidance relative to shopmonkey_create_appointment or shopmonkey_update_order, and no stated prerequisites.

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