timeiq_report_classic

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

No annotations are provided, and the description gives no behavioral details. It does not disclose side effects (e.g., data modification, authorization needs), output format, pagination, or any constraints beyond generation. For a tool with no annotations, the description must cover behavior, but it fails entirely.

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 5-word sentence, which is concise but far from sufficient. It lacks structure and omits essential information. Under-specification is not virtue in this context.

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 the tool has 7 parameters, no output schema, and no annotations, the description is extremely incomplete. It provides no details on report content, filtering semantics, or expected output. An AI agent cannot determine how to correctly invoke this tool.

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%, and the description does not explain any of the 7 parameters. Crucial parameters like start_date, end_date, clients, projects, services, people, and extras are left unexplained. An AI agent cannot infer how to use these inputs effectively.

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's purpose: generate a classic summary report in legacy layout. The verb 'Generate' and resource 'classic summary report' are specific. However, it does not explain what the report contains, and among many report siblings (timeiq_report_standard, timeiq_report_time, etc.), the term 'classic' and 'legacy' provide some differentiation but not full clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool versus other report tools (e.g., timeiq_report_standard, timeiq_report_time). There is no mention of prerequisites, contexts, or when not to use it.

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