get_time_report

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the date input format (YYYY-MM-DD), which is genuinely useful, but says nothing about rate limiting, the meaning of max_issues/concurrency, or whether results are paginated or truncated.

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 tight sentences with the report scope front-loaded and the date-format constraint appended. No filler, though the format note could be folded into the main sentence.

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?

An output schema exists, so return values need not be described, but for a 5-parameter tool with zero schema description coverage the description should explain the query parameter and the tuning parameters. It also omits the relationship to get_issue_time_report, leaving the agent under-equipped to choose correctly.

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 0% across 5 parameters, and the description only clarifies the date format for date_from/date_to. The required 'query' parameter's syntax and the roles of max_issues (default 50) and concurrency (default 5) are unexplained anywhere.

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?

Names a specific verb (build a summary report) and resource (Tracker tasks) and enumerates the breakdown dimensions: employees, tasks, queues, days. An agent understands the output shape. However, it never distinguishes itself from the sibling get_issue_time_report, which an agent must disambiguate on its own.

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 phrase 'from a Tracker query' implies the tool is query-driven aggregation, but there is no explicit when-to-use, when-not-to-use, or named alternative. The most likely confusion, get_time_report vs get_issue_time_report, is left entirely unresolved.

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