yougile_list_tasks

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

The description confirms the read-only behavior by referencing the read-only endpoint, which complements the readOnlyHint annotation. It adds value by explaining the endpoint's advantage (more filters), but does not disclose other behavioral details such as pagination limits or response structure. No contradiction with annotations.

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 concise at two sentences, front-loaded with the main purpose, and uses no filler words. Every sentence contributes useful information about filters and the endpoint choice.

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 tool's moderate complexity (6 optional params), full schema coverage, and annotations for safety, the description covers the essential usage. It lacks explicit return format details, but for a list tool this is a minor gap. The endpoint context and filter guidance make it 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?

The input schema already covers all 6 parameters with descriptions (100% coverage). The description highlights a few filter parameters (columnId, assignedTo, stickerId, title) but adds no new semantic detail beyond what the schema provides.

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 clearly states the tool's function: 'List tasks with filters.' It uses a specific verb and resource, and distinguishes itself from sibling tools like get_task by emphasizing the list and filter capability.

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?

The description provides clear context on when to use the tool through specific filter guidance and notes that the /task-list endpoint supports more filters than /tasks. However, it does not explicitly state exclusions or compare with sibling tools like get_task for single-task retrieval.

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