list_overdue_tasks

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

No annotations provided, so description carries full disclosure. It mentions return behavior (empty array) and underlying API methods. However, it does not explicitly state the tool is read-only, leaving slight ambiguity.

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?

Description is one paragraph but efficiently conveys all key information. Could benefit from slight restructuring (e.g., bullet points for scopes), but no fluff and content is well-organized.

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?

Covers all essential aspects: purpose, scopes, parameter conditions, API limitations, and return type. Without output schema, it appropriately describes return value. Thorough enough for an agent to use correctly.

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%, and description adds value by explaining when each parameter is required (e.g., project_id for 'project' scope) and linking to API methods. Minor redundancy with schema, but overall adds useful context.

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 lists overdue tasks with configurable scope, including specific scopes ('mine', 'all', 'project') and differentiates from sibling tools by focusing on overdue status.

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?

Provides explicit when-to-use for each scope, notes admin token requirement for 'all', and documents required parameters for 'project' scope. Also mentions unsupported API method to guide users away from invalid requests.

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