tasks_stats

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

With no annotations provided, the description must fully disclose behavioral traits. It does not state if this is a read-only operation, if it has side effects, or if it accesses external storage. The lack of any behavior cues beyond 'stats' 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 extremely short (three words), but brevity alone is not conciseness—it lacks essential information that warrants expansion. It is front-loaded but misses critical context that should earn 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?

Given the tool has no parameters and no annotations, the description should clarify the output (which appears to have an output schema) and behavior. It fails to describe what the returned statistics include or how they relate to the task store, leaving the agent uninformed.

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 zero parameters, so parameter semantics are not relevant here. The description does not need to add meaning beyond what the schema provides. Baseline score reflects the schema coverage being 100%.

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 'Task store stats.' vaguely indicates it provides statistics about a task store, but it doesn't specify what specific statistics, the source of the data, or how it distinguishes from sibling tools like cache_stats or memory_stats. The verb is implied (get/retrieve) but not explicitly stated.

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?

No guidance on when to use this tool versus other stats tools (e.g., memory_stats, cache_stats). No context about prerequisites or intended use cases is provided.

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