aiworkhub_task_usage_report

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

With no annotations provided, the description carries the full behavioral burden. It implies a read via 'Return' but does not disclose whether results are aggregated, what time window is covered, whether output is paginated, or any auth/permission requirements. It adds essentially nothing beyond the verb.

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 single sentence is front-loaded and free of padding, which is structurally sound. It is under-specified rather than overly verbose, so it earns a middling score for form rather than content.

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?

An output schema exists, so return values need not be explained, but for a three-parameter filtered report with zero schema descriptions the definition should clarify filter semantics and read-only nature. It falls short of what an agent needs to invoke it confidently.

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 description coverage is 0% across three parameters (topic, runner, status), so the description must compensate and does not. 'Optionally filtered' acknowledges the filters exist but never identifies which fields are filterable or how values are matched, leaving the agent to guess from bare parameter names.

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 names a resource ('task usage report') and an action ('Return'), so the agent knows it is a reporting read. However, neither the scope of the report nor what distinguishes it from siblings like aiworkhub_manager_skill_usage, aiworkhub_manager_recipe_usage, or aiworkhub_task_cost_ledger is stated. The purpose is implied but not specific.

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 only guidance is 'optionally filtered', which signals filters exist but never says when to use this report versus other usage/ledger tools. There is no when-to-use, when-not-to-use, or named alternative anywhere in the text.

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