listTasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List tasks,' omitting important context such as read-only nature, pagination behavior, return format, or any side effects. The agent is left to infer everything from the parameter 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?

At two words, the description is extremely concise but under-specified. This is not good conciseness; it is a lack of substance. Every sentence should add value, and this description adds almost no value beyond the tool name.

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 tool has 5 optional parameters and no output schema, so the description should at least mention pagination, sorting, or return type. No such context is provided, making the description inadequate for an agent to understand the tool's full capabilities and constraints.

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?

All five parameters have descriptions in the input schema, achieving 100% schema description coverage, so the baseline is 3. The tool description itself adds no additional meaning about how the parameters work together, defaults, or usage patterns. The schema descriptions are generic but acceptable.

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 states the action ('List') and the resource ('tasks'), which is clear and unambiguous. However, it does not differentiate from sibling list tools beyond the resource name; there is no mention of scope, filtering, or other distinguishing details. This is essentially a human-readable version of the tool name.

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?

There is no guidance on when to use this tool versus alternatives like listNotes or listCalls. The description simply repeats the tool's function and offers no decision support, prerequisites, or exclusions.

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