dooray_list_tasks

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a list operation but doesn't describe pagination behavior (though 'page' and 'size' parameters suggest it), rate limits, authentication needs, or what happens with invalid filters. The mention of 'optional filtering' is minimal behavioral context.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a list operation and front-loads the core purpose. Every word earns its place.

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 tool has 9 parameters with 0% schema coverage and no annotations, the description is incomplete—it doesn't explain filtering options or behavioral details. However, the presence of an output schema reduces the need to describe return values, making it minimally adequate but with clear gaps.

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 description coverage is 0%, so the description must compensate for 9 undocumented parameters. It only mentions 'optional filtering' generically without explaining what filters are available (workflow_class, to_member_ids, etc.) or their semantics. This adds minimal value beyond the parameter names in the schema.

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 from Dooray project'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'dooray_get_task' (singular vs. plural) or 'dooray_list_comments' (tasks vs. comments), which prevents a perfect score.

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 mentions 'optional filtering' which implies some usage context, but provides no explicit guidance on when to use this tool versus alternatives like 'dooray_get_task' for single tasks or 'dooray_list_comments' for comments. No prerequisites or exclusions are mentioned.

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