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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds two things they don't: a hard cap of 50 results and recency ordering, plus the permission requirement on the project. It stops short of explaining pagination or how to retrieve more than 50, which is the remaining behavioral gap.

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?

A single front-loaded sentence with no filler; the result cap and scope constraint appear before the optional filter detail, which is the right ordering for an agent scanning for eligibility.

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 two-parameter read tool with an output schema, the description need not explain returns. However, the query filter semantics and the behavior past the 50-result cap are left unresolved, which are the details an agent needs to call this correctly against a large project.

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%, so the description must carry parameter meaning. It maps 'project' to project_id and 'filtering subjects' to query, but 'filtering subjects' is ambiguous about matching semantics (substring vs exact, server-side vs client-side), and it never states that project_id is required.

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 packages) with scope qualifiers: up to 50, recent, within a permitted project. This cleanly separates it from the sibling single-item getters and the create/update tools, though it never names an alternative explicitly.

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?

Usage is only implied: a 'list' tool is understood to be for browsing, versus openproject_get_work_package for a single item. The phrase 'in a permitted project' hints at a permission prerequisite but no when-to-use, when-not-to-use, or alternative routing is stated.

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