list_tasks_by_category

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

Annotations already provide readOnlyHint and openWorldHint. The description adds useful context: it lists all tasks across every list and mentions the OData filter syntax. However, it does not disclose potential limits like pagination or the effect of top_per_list on 'ALL tasks'.

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 very concise (two sentences), front-loading the purpose and providing a useful OData syntax hint. However, it could be slightly more structured to cover all parameters without becoming verbose.

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?

With 4 parameters and no output schema, the description inadequately explains top_per_list and include_completed, and creates ambiguity with 'ALL tasks'. It fails to clarify the output format beyond the verbose parameter's schema description.

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?

Only the verbose parameter has a description in the schema (25% coverage). The description adds OData filter details for category but fails to explain top_per_list and include_completed. Moreover, 'List ALL tasks' contradicts the limiting effect of top_per_list.

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 verb (list) and resource (tasks), specifies scope (across every list), and provides the OData filter syntax. It distinguishes itself from siblings like list_all_tasks or search_tasks by focusing on category filtering.

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 when to use (when filtering by category) but does not explicitly mention when not to use or suggest alternatives like list_all_tasks or search_tasks for other filtering needs.

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