woo_get_order_notes

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

No annotations are provided, so the description carries the full burden. 'Get' weakly implies a read, but nothing is said about authentication, whether notes are private/customer-facing, pagination, or return format. The description adds essentially no behavioral context.

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?

It is a single front-loaded phrase with zero waste, but it is under-specified rather than genuinely concise; the terseness buys no clarity and omits useful context an agent would need.

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 annotations, no output schema, and only two documented params, the description should explain what the notes contain (visibility, ordering, pagination) and how it differs from sibling note/order tools. As written it is too thin for the agent to call confidently.

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% — both 'id' (Order ID) and 'site' (see list_sites) are documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema.

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 name and description give a clear verb+resource ('Get order notes'), so an agent knows it retrieves notes for an order. However, it does nothing to distinguish itself from close siblings like woo_add_order_note, woo_get_order, or woo_list_orders — the description is a bare restatement of the noun phrase.

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 indication of when to use this versus woo_get_order or woo_add_order_note, nor any mention of prerequisites such as needing an existing order ID from list_sites/woo_list_orders. Usage is only implied by the name.

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