stale_tasks

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

No annotations provided, so description carries full burden. It discloses auth requirements (V1+V2), the multi-value filter behavior, and the data domain (active, stale tasks). It lacks details on pagination, sorting, or default limit, but is still informative.

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?

Extremely concise: two sentences plus a compact bracket line encoding category, auth, related tools, and a filter note. Every part adds value and front-loads purpose.

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?

While the description captures core purpose and filter behavior, it omits details like return format (fields, structure), default limit, sorting order, and definition of 'active'. For a query tool with no output schema, these would help an agent use the tool effectively.

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 description must compensate. It explains that multi-value filters accept list or string, but does not explain older_than_days or text_query semantics. Parameter names are somewhat self-explanatory, but more detail would improve usability.

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 it returns active tasks not modified recently, distinguishing it from sibling tools like query_tasks (general) and overdue_tasks (overdue instead of stale).

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 implicitly suggests use for finding stale tasks via the verb 'return' and the 'active tasks not modified recently' phrase. The related tools are listed but no explicit guidance on when to prefer this tool over alternatives.

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