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 fully covered without the description. The description adds that results are requester-submitted, which is useful orientation, but says nothing about default ordering, auto-pagination behavior, or result shape. With annotations carrying the safety burden, a 3 is appropriate.

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 compact sentences with zero filler, and the resource identification is front-loaded before the filtering capability. Every clause earns its place.

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?

A six-parameter read tool with no output schema and no parameter exclusions. The description covers what the tool returns at a high level but omits mention of site_id, search, or the automatic pagination contract, leaving the schema to carry all of that.

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 description's enumeration of status values (PENDING_REVIEW, APPROVED, REJECTED) and priority merely restates what the schema already documents. Baseline 3 applies; no additional syntax or format meaning is added.

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 (list) and resource (work requests), plus the scope qualifier that these are requester-submitted items. It does not, however, differentiate itself from the many sibling list_* tools or from list_work_orders, so it falls just short of 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 names the filterable dimensions but gives no when-to-use guidance, no distinction from get_work_request or list_work_orders, and no prerequisites. Usage is only weakly implied.

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