Issue time tracking

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

Annotations indicate the tool is not read-only and not destructive, but the description adds little extra. It doesn't mention that 'reset_estimate' and 'reset_spent' clear existing values, or that 'estimate' overwrites, which is important behavioral context beyond the annotations.

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?

Single sentence, no filler, directly states the purpose. It is appropriately brief.

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 5 distinct actions and no output schema, the description is too thin. It doesn't enumerate the actions or describe their effects, leaving an agent without enough context to correctly select an action.

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?

Description does not explain any parameters. With 60% schema coverage, the missing descriptions for 'action' and 'issue_iid' are not compensated. The high-level 'reads or updates' doesn't map to the specific actions in the enum.

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 reads or updates estimate and spent time on an issue, using a specific verb ('reads or updates') and resource ('estimate and spent time on an issue'). This distinguishes it from sibling issue tools that handle general issue fields.

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 explicit when-to-use guidance is provided. The intended use is implied by the tool name and description, but it doesn't compare with alternatives like gitlab_update_issue or state exclusions.

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