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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the auth model: local WordPress authentication is used and no WooCommerce REST API keys are required, which tells the agent this call will work without separate credential setup.

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 with the purpose front-loaded and the operational note second; nothing is padded. The reference to the upstream `get_order_note` method is somewhat incidental but supports the auth claim.

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?

This is a low-complexity single-record read with fully described required parameters and rich annotations, so invocation requirements are largely covered. However, there is no output schema and the description says nothing about what a note record contains, which leaves a small gap for an agent deciding whether this call returns what it needs.

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%, and the schema itself already documents all three parameters, including the instruction to call list_sites first and not to pass a URL or post ID. The description adds no parameter meaning of its own, so the baseline 3 applies.

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?

"Gets one note for a WooCommerce order" names a specific verb (get) and a specific resource (a single order note), and the singular framing implicitly separates it from the plural sibling wc_get_order_notes. It does not explicitly name or contrast with any sibling, so it stops short of a 5.

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 description offers no when-to-use or when-not-to-use guidance and never points to alternatives such as wc_get_order_notes for listing or wc_get_order for the parent order. The only context given concerns authentication and implementation parity, which does not help an agent choose between tools.

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