Get Stuck List

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

With no annotations, the description carries full burden. It discloses the output includes days_stale, suggested triage action, and a render field with tiered rendering guidance. It does not mention auth or rate limits, but for a read-only tool this is acceptable.

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?

Three sentences front-load the purpose and key behavioral points. Every sentence adds value: what it returns, why use it, and a critical note about the render field. No unnecessary words.

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?

The description covers the output content and the render field, which is helpful for agent usage. With 3 well-described parameters and no output schema, it provides sufficient context for effective use, though some edge cases (e.g., empty results) are not addressed.

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 coverage is 100%, so baseline is 3. The description adds no new meaning beyond what the schema already provides (scope, timezone, max_age_days). The effect of max_age_days is implied but not explicitly tied to the parameter.

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 clearly states the tool surfaces stuck, stale, and overdue tasks needing triage, specifying the three categories (untouched, blocked, overdue). This differentiates it from sibling tools like get_task or list_tasks, which serve broader task retrieval purposes.

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 usage for triaging tasks but does not explicitly state when to prefer this tool over alternatives or when not to use it. No guidance on prerequisites or exclusions, which is a gap given the number of sibling tools.

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