summarize_tasks

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'summarize' and 'statistics', which implies a read operation, but does not explicitly confirm read-only behavior, potential side effects, or what exactly is returned. For a tool with no annotations, this transparency is insufficient.

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 a single sentence, making it concise and front-loaded. However, it is somewhat under-specified. Still, it wastes no words and earns its place.

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 has a single optional parameter and no output schema. The description does not describe the return value (what statistics are included, format), which is a critical gap. A simple summary tool should at least hint at the output structure. This is inadequate given the lack of output schema.

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% (the single parameter projectId is described in the input schema). The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already clarifies the parameter's role.

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 states a specific verb-resource combination: 'Get a summary of tasks with statistics'. It clearly indicates that this tool returns aggregated data rather than individual tasks, distinguishing it from siblings like list_tasks or get_task. However, it could be more precise about the type of statistics.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when to favor it over list_tasks, or when not to use it. Given siblings like list_tasks and get_task, explicit context would help the agent choose correctly.

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