get_projects_for_review

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the selection criterion based on next review date, but it does not describe return ordering, pagination behavior, or any permissions/rate-limit context beyond the schema-documented limit.

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?

The description is a single efficient sentence with the core selection criterion front-loaded. Every phrase earns its place and there is no redundant restatement of the tool name.

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 simple read/list tool with two optional, fully documented parameters and no output schema, the description gives the essential selection logic. It could mention ordering or what a returned project entry contains, but those gaps are minor.

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%, so both optional parameters (limit and includeOnHold) are already documented in the input schema. The description adds no parameter-level meaning beyond the schema, which is acceptable at baseline 3.

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 uses a clear verb and resource: getting projects due for review, and defines 'due' as next review date in the past or today. It is specific about the resource subset, though it does not explicitly name sibling alternatives such as list_projects or get_project_by_id.

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 implies the use case by defining 'due for review,' but it gives no explicit guidance on when to choose this tool over list_projects, get_project_by_id, or batch_mark_reviewed. There are no stated prerequisites or exclusions.

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