get_cycle_time

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

No annotations provided. Description explains it returns average cycle time at process level, but does not specify if it's a single value or per-case, nor the time range scope. 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?

Three sentences, front-loaded with the purpose, no redundant information, and efficient use of text.

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?

Tool is simple with output schema covering return structure, but missing parameter semantics and behavioral details about scope. Adequate for a basic retrieval but could be more complete.

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 coverage is 0% with no description of the required log_id parameter. Description does not explain what log_id is or its format, leaving a significant gap for a single-parameter tool.

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?

Clearly states tool returns average cycle time, defines it as 'seconds between case completions', and explicitly distinguishes from sibling get_case_durations.

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?

Explicitly contrasts with get_case_durations, indicating this is for throughput measurement and capacity planning, but does not provide explicit when-not-to-use or alternatives beyond the stated sibling.

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