time_list_timers

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

Discloses that it returns only active/running timers, which is a key behavioral trait. With no annotations, the description partially fills the gap but omits details like pagination behavior or potential rate limits. Adequate but not comprehensive.

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?

Single sentence with parenthetical clarification, front-loads key information. Every word adds value; no wasted space.

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?

No output schema, so description should hint at return structure (e.g., fields like timer ID, start time). Without that, completeness is only moderate. Adequate for simple list tool given sibling 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?

Schema provides 100% coverage with clear descriptions for all 3 parameters. The tool description adds context about 'active/running' and 'automated billing workflows', but doesn't enhance parameter meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states it lists ticket timers that are active/running across tickets, with specific filtering options. This distinguishes it from siblings like 'time_list_timelogs' which likely list completed timelogs.

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?

Mentions filtering by customer or billing status and supports automated billing workflows, suggesting appropriate contexts. However, lacks explicit guidance on when to use this tool over similar tools like 'time_list_timelogs' or 'tickets_list'.

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