get_task_report

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

Declares 'Read-only' upfront, clearly indicating no side effects. No annotations to contradict; description carries full burden for behavioral disclosure.

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?

Concise three-sentence structure: purpose, list of examples, filters explanation, and usage guidance. No unnecessary words; well-organized.

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?

Completely covers tool's function, parameters, usage context, and output nature. With output schema present, no need to detail return values. For a read-only tool, all essential aspects are addressed.

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?

Despite 0% schema description coverage, description adds rich meaning: report_name explained with examples, filters described as Taskwarrior syntax with example usage. Greatly enhances 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?

Clearly states 'Run a named Taskwarrior report and return its output. Read-only.' with specific verb and resource. Lists built-in report names and custom support, distinguishing from sibling list_tasks.

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 states when to use ('formatted report view or urgency ordering is more useful') and when to use sibling ('Use list_tasks for raw JSON output'). Provides guidance on filters syntax.

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