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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds nothing about pagination, default result limits, or filtering behavior — the useful behavioral facts for a list endpoint — beyond a pointer to describe_operation.

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 short, but the first two sentences are verbatim duplicates and the operation ID is noise to the agent. The one substantive clause (the describe_operation pointer) is buried at the end.

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?

No output schema exists, so the description should describe the return shape and filtering, and it does neither. With a nested free-form query object and an undocumented params object, the definition is not sufficient to invoke the tool correctly without first calling describe_operation.

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 0% and the two parameters are untyped opaque objects: a free-form `query` (additionalProperties: {}) and an empty `params` object. The description says nothing about what belongs in `query` (filters, pagination fields) or why `params` exists, so the agent has no way to construct a meaningful request without a separate call.

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 only repeats the HTTP method and path ("GET /api/work-orders") plus an opaque operation ID. It conveys the resource family but is essentially a restatement of the name/title, with no statement of what the call returns or what scope of work orders it covers.

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 only actionable hint is that "describe_operation provides native request schemas," which points at one sibling for a different purpose. There is no guidance on when to use this list endpoint versus get_work_orders_by_id, get_work_orders_stats_summary, search_operations, or execute_read.

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