List Task Items Assignee Options

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

Annotations already indicate readOnly, not destructive, idempotent. Description adds pagination metadata and endpoint details, which are useful but not essential beyond annotations. No contradictions.

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?

Description is relatively concise (3 sentences) but includes redundant endpoint info and an inconsistency. It could be clearer by focusing solely on assignee options.

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?

With no output schema, the description should accurately describe the return value. It incorrectly says 'JSON array of Tasks' instead of Users. This is a significant gap for a simple list tool.

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 mentions project_id as required and pagination parameters, but this adds no new meaning beyond the schema descriptions.

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 states it returns users assignable to task items, which is clear. However, the second sentence says 'enumerate Tasks', causing confusion about the tool's actual output. This inconsistency reduces clarity.

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?

Provides generic guidance for paginated overview and filtering but fails to distinguish from sibling tools like 'list_task_items' or 'list_assignable_users'. No when-not-to-use or alternatives mentioned.

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