get-billable-time-report

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

The description labels the tool as 'get-' suggesting a read-only operation, but lacks explicit behavioral details such as read-only nature, rate limits, or response structure. Without annotations, the description carries the burden and is only minimally informative.

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 a single, well-structured sentence that communicates the core functionality without extraneous words. Every part adds value.

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?

With no output schema, the description does not clarify the report's structure, fields, or pagination. It is adequate for understanding the tool's purpose but leaves gaps in what the agent can expect as output.

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?

Input schema coverage is 100% with clear descriptions for all four parameters. The description does not add meaningful extra semantics beyond summarizing the breakdown dimensions already covered by the schema descriptions.

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 the tool retrieves 'a detailed report of billable vs non-billable logged time with breakdown by person and project,' which is specific and distinct from sibling tools like get-time-report or get-people-utilization-report.

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 description implies use for analyzing billable vs non-billable time but does not explicitly state when to use this tool over alternatives or provide any exclusion criteria. No guidance on prerequisites or context.

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