get_task_statistics

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

No annotations are provided, so the description must carry the full burden. It fails to clearly state that this is a read operation returning profiling data, and the phrase 'Enables CPU task profiling' is misleading for a getter. The output format or behavior is not described.

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 short (three segments) but includes extraneous details about turning off and default values that are more appropriate for a setter. It is not concise in its purpose.

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 absence of an output schema, the description should explain what the tool returns. It only vaguely mentions 'CPU task profiling visible via `tasks` CLI command' without specifying the format or structure. The tool is part of a large family of get_* tools but lacks integration context.

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 no parameter info is needed. However, the description includes '[INT8, default: ON]' which is irrelevant and potentially confusing, as it suggests a parameter that does not exist. This adds no value and undermines clarity.

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 'Get task_statistics' but then says 'Enables CPU task profiling', which conflates a getter with an enabling action. The purpose is somewhat clear as retrieving profiling data, but the verb mismatch reduces clarity. It does distinguish from siblings by referring to task statistics specifically.

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 explicit guidance on when to use this tool versus alternatives like 'get_tasks' or 'cli_status'. The mention 'Turn OFF to reduce overhead' is more relevant to a setter and does not help with tool selection.

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