List tasks

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses result capping ('default 50'), the motivation ('a large backlog cannot flood the conversation'), truncation signaling, and the Sunday-first dayOfWeek convention that differs from weekly reports. These are non-obvious behaviors not visible in the schema.

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?

Two sentences, front-loaded with the read-only safety cue and a direct action, followed by the caveats that matter. There is no filler.

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?

For a six-parameter list tool with no output schema, it covers the major invocation decisions: filters, statuses, cap/truncation, and date-ordering gotcha. It stops short of describing the response structure or sorting, but those are minor for correctly invoking the tool.

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 the schema already documents all six parameters with defaults, enums, and id provenance rules. The description adds useful context for limit and dayOfWeek, but mostly restates statuses and filters rather than introducing new parameter meaning, matching the baseline for high schema coverage.

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 opens with 'READ ONLY. Lists tasks' — a specific verb and resource — and enumerates the optional filters (status, goal, schedule block, day of week). This clearly separates the tool from siblings like list_goals or list_time_entries.

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?

It states the tool is for listing tasks and gives the filter dimensions and default cap, so an agent can infer when to call it. It does not explicitly name alternatives or exclusion conditions, but none of the sibling names compete for the same task-listing purpose.

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