get_time_report

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. Description adds that it 'shows... all time entries' but no extra behavioral context like pagination, limits, or required permissions.

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?

Two sentences, 19 words, no fluff. Purpose and key output fields front-loaded. Efficient and easy to parse.

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?

Given low complexity (2 params with simple types) and presence of output schema, description covers purpose and output. However, missing usage guidelines and parameter semantics make it less complete for an agent to confidently invoke.

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 has 100% coverage but the descriptions are generic ('a string that will be trimmed'). Description does not clarify that 'project' and 'identifier' refer to the issue's project and identifier, missing an opportunity to add meaning beyond the schema.

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 it retrieves a time tracking report for a Huly issue, listing specific fields (total time, estimation, remaining time, entries). Uses specific verb 'Get' and resource 'time tracking report', distinguishing from sibling tools like log_time or list_time_spend_reports.

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?

No guidance on when to use this tool versus alternatives like get_detailed_time_report or list_time_spend_reports. No prerequisites or exclusions given, leaving the agent to infer usage context.

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