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

Annotations already cover read-only/safe/non-open-world, and the description adds real value on top: it documents the 'halted' states ('owner_lost' vs 'refused' with 'lastError') and that filing happens in the owner's name. It stops short of describing ordering or how many schedules are returned.

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?

Front-loaded correctly with the core concept, but it is a single sprawling sentence with stacked parentheticals that is harder to parse than necessary. Every clause carries information, yet the density works against scanability.

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?

Since there is no output schema, explaining the returned fields (cadence, nextDay, dueInDays, halted reasons, lastIssueKey) is exactly the needed compensation and it is done thoroughly. Only return ordering/count details are missing.

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?

The single 'project' parameter is fully documented in the schema ('The project key, e.g. PM'), so the schema does the heavy lifting. The description adds nothing about the parameter itself, only about returned fields.

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?

Opens with a specific verb+resource ('A project's RECURRING ISSUES ... issues it files by itself on a calendar') and gives concrete examples (monthly report, quarterly review). It doesn't name the sibling set_issue_schedule/delete_issue_schedule, so differentiation is implied by the list/set naming rather than stated.

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 by the word 'List' and the read framing. It never says to use this before set_issue_schedule or delete_issue_schedule, nor when a schedule list is the right lookup versus find_issues. The access note ('Any member may read them') is the only contextual guidance.

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