find-completed-tasks

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

With annotations already declaring readOnlyHint, idempotentHint, and destructiveHint, the description adds valuable behavioral details: the default 7-day window when since/until are omitted, and that all collaborators are included by default unless responsibleUser is set. This goes beyond the structured metadata to clarify scope and default behavior.

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 three sentences, front-loaded with the core purpose, and every sentence provides meaningful information: purpose, default date behavior, and the responsibleUser caveat. No filler or repetition of schema details.

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 complexity (12 parameters, output schema, rich annotations), the description covers critical behavioral aspects not evident from structured data: default date window, collaborator inclusion, and a prerequisite for personal queries. It doesn't mention pagination or sorting, but the output schema and parameter descriptions fill those gaps adequately.

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 the baseline is 3. The description adds extra meaning beyond the schema by explaining the default 7-day window for since/until and clarifying that responsibleUser is required for person-specific queries. This supplements the parameter descriptions with practical usage semantics.

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 opens with 'Get completed tasks,' which clearly states the tool's primary function with a specific verb and resource. It distinguishes itself from siblings like find-tasks or find-tasks-by-date by focusing on completed tasks, making its purpose unambiguous.

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 practical usage context: since/until are optional with a 7-day default window, and it explicitly notes that person-specific queries require the responsibleUser parameter. While it doesn't name alternatives directly, the guidance implies when this tool is appropriate versus others, and it clearly states a key prerequisite for personal queries.

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