get_tasks

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

No annotations are present, so the description must carry the full burden. It does not disclose pagination behavior, retrieval scope (e.g., all tasks for the user or a project), or any side effects. The word 'list' implies read-only, but this is not explicit.

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 extremely concise at 4 words. While it is not wasteful, it may be too brief given the tool has 4 parameters and no output schema. It is front-loaded with the core action, but could include more detail without harming conciseness.

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 lack of output schema and the presence of many sibling tools, the description is incomplete. It does not explain pagination, default behavior when no filters are applied, what 'all tasks' means, or how filters interact. A more complete description would address these 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?

The input schema has 100% description coverage (each parameter has a basic description). The tool description adds nothing beyond the schema, so the baseline score of 3 is appropriate. The schema descriptions are minimal (e.g., 'Search query' without specifying fields), but the tool description does not improve them.

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 'List all tasks with optional filtering' clearly states the verb (list) and resource (all tasks), and hints at filtering capability. However, it does not explicitly distinguish from the sibling tool 'get_task' which retrieves a single task, but the name makes the distinction obvious.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_task' or which filtering parameters to use in different contexts. The description simply states the capability without any contextual advice.

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