List invoices

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the paid-plan requirement, which is useful, but does not disclose pagination behavior or defaults beyond what the schema already states. This is acceptable but minimal.

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 and front-loaded, using only two fragments. It is concise, though the first fragment is nearly redundant with the title, containing only 'workspace' as added scope. It earns a 4 for efficiency, not a 5 because it lacks substantive 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?

For a tool with six parameters, including pagination and workspace resolution logic, and no output schema, this two-fragment description is severely under-specified. It does not explain return format, pagination behavior, or the meaning of all_pages/status beyond what the schema already documents. The high-level context is insufficient for an agent to fully understand the tool's capabilities.

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 100%, so all six parameters have meaningful descriptions in the input schema. The tool description itself does not add any parameter-specific context, meeting the baseline but not exceeding it.

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 'Invoices in the workspace' identifies the resource and workspace scope but lacks an explicit verb; it relies on the title 'List invoices' to convey the action. It does not differentiate from sibling list tools like clockify_list_projects or clockify_list_clients.

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 usage-related information is 'Needs a paid plan,' which is a prerequisite, not guidance on when to use this tool over alternatives. No exclusions or alternative tool recommendations are provided, leaving the agent to infer usage from the tool name.

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