list_tasks

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

Despite no annotations, description discloses pagination defaults (50), search matching behavior (every word must match), and parameter constraints (max 200). Does not mention read-only nature explicitly, but implied.

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 concise sentences: first states core purpose and filters, second gives example usage. No fluff, every sentence 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?

Covers pagination and search behavior well. Lacks description of return format or error cases, but for a list tool with 8 params and no output schema, it is reasonably complete.

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 coverage is 100%, so baseline is 3. Description adds value by summarizing defaults (limit=50, offset=0) and clarifying multi-term matching for q, case-insensitive tag, comma-separated status, and special values for assignee and parent.

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?

Description clearly states 'List tasks in a project with optional filters' – specific verb, resource, and scope. Differentiates from siblings like get_task (single task) and create_task.

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?

Explicit guidance on using q for keyword search and limit/offset for pagination. Lacks exclusionary guidance or when-not-to-use, but clear context for common scenarios.

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