task_list

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

No annotations provided, so description carries full burden. Discloses default filtering (open tasks, priority order) and filterable parameters. While it doesn't mention side effects or auth, the read-only nature is implied by 'list'. Reasonably transparent 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 are concise and front-loaded with the primary action. Every sentence adds value: first states action and context, second adds filters and defaults. No wasted words.

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 no output schema, the description covers core functionality well: listing with defaults and filtering. Could add return format or pagination hint, but for a simple list tool it is sufficiently 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 has 100% coverage with basic descriptions. Description adds value by explaining defaults and ordering ('Defaults to open tasks in priority order') and clarifying how filters relate to the default list. This enhances understanding beyond bare 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?

Description clearly states 'List tasks in the shared queue.' with specific verb (list), resource (tasks), and context (shared queue). Distinguishes from siblings like agent_list, task_create, and task_show by focusing on listing tasks with 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?

Description provides default behavior ('open tasks in priority order') and filtering options (status, assignee). Implicitly guides when to use (listing tasks) but lacks explicit when-not-to-use or alternatives, though sibling tools are listed for context.

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