timeiq_timesheet_with_issues

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

No annotations are provided, so the description carries full burden. It does not disclose whether the operation is read-only, has side effects, or requires specific permissions. Listing 'issues' suggests a read operation, but this is not confirmed. The description lacks behavioral context beyond the basic listing action.

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 that conveys the essential purpose and examples. No extraneous words. Front-loaded with the main action and resource. Every word serves a purpose.

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 no output schema, the description should ideally provide hints about return value structure. It does not mention fields, pagination, or output format. However, for a simple list of flagged timesheets, the description is minimally adequate. Lacks detail for full contextual completeness.

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?

There are zero parameters, and the schema coverage is 100%. Per guidelines, 0 parameters earns a baseline of 4. The description adds no parameter info since none exist, which is appropriate. No additional semantics needed 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?

The description clearly states the verb 'List' and resource 'timesheets flagged with issues', with examples (overbooked, missing required time). It effectively distinguishes from other timesheet tools like timeiq_timesheet_list which likely shows all timesheets.

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 usage for problematic timesheets but does not explicitly state when to use this tool versus alternatives. No 'when not to use' or alternative tool names are given. Usage is inferred from context.

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