get_case_tasks

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

The description discloses that it lists tasks with optional filters, and mentions a default limit. Since no annotations exist, the description adequately conveys a read-only behavior, though it doesn't explicitly state non-destructiveness or auth needs.

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 well-structured as a docstring with a clear main sentence followed by parameter explanations. Every sentence serves a purpose without redundancy, being both concise and informative.

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 5 parameters, 1 required, and an existing output schema, the description thoroughly explains all inputs. It lacks error handling or edge case behavior but adequately covers the core functionality.

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 no descriptions (0% coverage), so the description fully compensates by explaining each parameter: case_id, sort (with formatting), date filters (ISO 8601 or timestamp), and limit (default 50). This adds significant meaning 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?

The description clearly states 'List all tasks associated with a specific Case,' specifying the verb and resource. It distinguishes from sibling tools like create_task or get_case, which have different purposes.

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 implicitly indicates when to use (to list tasks for a case) but does not explicitly mention when not to use or compare with alternatives. It provides clear context without exclusions.

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