timeiq_report_incomplete_time

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

Annotations are entirely absent, so the description must fully disclose behavioral traits. It only states the tool identifies people but does not mention whether the tool is read-only, what the output format is, or any restrictions. For a reporting tool, this is insufficient.

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 sentence, which is concise but poorly structured. It lacks any breakdown of usage, parameters, or output, making it minimally viable.

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 7 parameters, 0% schema coverage, no output schema, and no annotations, the description is vastly incomplete. The agent cannot determine what the tool returns, how to format inputs, or what constraints apply.

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?

The input schema has 7 parameters with 0% description coverage. The description does not explain the meaning or format of any parameter, including required fields like start_date and end_date. This forces the agent to guess their purpose.

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 identifies people with incomplete, un-submitted, or open timers. It uses a specific verb ('identify') and resource ('people with...timers'), distinguishing it from sibling report tools that focus on different aspects of time reporting.

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 is provided on when to use this tool versus alternatives like timeiq_report_missing_time or timeiq_report_time. There is no mention of prerequisites, exclusions, or comparative scenarios, leaving the agent to infer usage from the tool name alone.

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