list_tasks

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

Without annotations, description discloses pagination and fetch_all behavior. Omits read-only nature or permission needs, but sufficient for a list operation.

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, no fluff, front-loaded key action and features.

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?

Adequate for core functionality but incomplete given 10 parameters, no output schema, no annotations. Lacks details on return format and parameter meanings.

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?

0% schema coverage; description only mentions name/active filtering and fetch_all. Does not explain required project_id or optional params like workspace_id, sort, page.

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?

Clearly states 'List tasks on a project' with filtering and pagination options. Distinguishes from sibling tools like get_task or list_projects.

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?

Implies usage for listing/filtering tasks but no explicit when-to-use or alternatives. Lacks guidance on choosing over other list tools.

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