get-task-stats

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get statistics about all tasks', which implies a read-only operation, but doesn't specify what kind of statistics (e.g., counts, averages, trends), whether it requires permissions, or how data is returned (e.g., format, pagination). This leaves significant gaps in understanding the tool's 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 a single, efficient sentence: 'Get statistics about all tasks.' It is front-loaded and wastes no words, making it easy to parse quickly. Every word earns its place by conveying the core action and scope.

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 complexity of statistical tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what statistics are returned (e.g., numerical summaries, charts), how they are aggregated, or any limitations. For a tool that likely provides detailed data, this minimal description fails to give enough context for effective use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it could have clarified that no inputs are required. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 'Get statistics about all tasks' clearly states the verb ('Get') and resource ('statistics about all tasks'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-task-status' or 'get-task-result', leaving ambiguity about what specific statistics are provided versus status or result information.

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. With siblings like 'get-task-status', 'get-task-result', and 'list-tasks', there's no indication of whether this tool is for aggregated metrics, performance data, or other statistical insights, nor any prerequisites or exclusions mentioned.

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