list_anytime

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

The description defines the filter criteria (schedule='anytime', not completed, not trashed), adding behavioral context beyond the tool name. However, without annotations, it does not disclose other traits like read-only nature or pagination behavior.

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 concise with two sentences: one stating the purpose and one defining the filter. No redundant information, and the key behavior is front-loaded.

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?

Given the presence of an output schema and the simplicity of the tool, the description adequately defines what the tool does and what tasks it returns. The lack of parameter details is a minor gap but does not severely hinder overall completeness.

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 description provides no explanation for the two parameters (limit and offset). With 0% schema description coverage, the description should compensate but fails to add any parameter semantics.

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 tasks from the 'Anytime' list, which is a specific resource. It defines 'Anytime' as tasks available to work on without a specific date, distinguishing it from sibling tools like list_today or list_inbox.

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 tasks without a specific date but does not explicitly state when to use this tool versus alternatives. No guidance on exclusion criteria or comparative context is provided.

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