get_completed_tasks

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

No annotations provided, so description must carry full burden. Description mentions 'efficient date filtering and categorization' but doesn't explain categorization or output format. For a read operation, side effects are minimal, but further behavioral details (e.g., pagination, limits) are absent.

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?

Three sentences are efficient and front-loaded with purpose. However, omission of parameter documentation reduces value. Structure is clean but incomplete.

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?

The tool is simple with one optional param and an output schema (content not shown). Description covers purpose and usage context but lacks detail on return format, categorization meaning, or debug behavior. Adequate but not thorough.

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 one parameter 'debug' with 0% description coverage. The description fails to mention or define this parameter, leaving the agent without guidance on its purpose or usage.

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 'Get completed tasks from past 7 days', specifying verb, resource, and default scope. It distinguishes from sibling tools like get_completed_tasks_for_date and get_productivity_summary_for_time_range by mentioning them as alternatives for specific or custom ranges.

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?

Explicitly says when to use: 'review recent accomplishments or productivity patterns'. Also provides alternative tools for specific dates and custom time ranges, guiding selection effectively.

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