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

While annotations mark it as destructive, the description adds essential behavioral details: how repeated calls are handled (duplicates), and the functional meaning of the 'CONCEPT' status (it keeps the entry editable). This goes beyond simple CRUD descriptions.

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 highly concise and efficiently structured. It front-loads the primary action and separates the functional mechanics (duplicates/status) from the core API reference without wasted language.

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 complexity of managing time registration, the description is very complete. It explains the core operation, the potential pitfalls (duplicates), the status system, and the specific Gripp API endpoint, which adds necessary technical context.

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?

Since the input schema provides 100% coverage with descriptive parameter definitions, the description does not need to elaborate on specific field meanings. It remains at the baseline score, providing high-level process context instead of semantic detail.

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 starts with a clear 'WRITE' directive and specifies the resource (hours) and context (on a project/task) within the Gripp system. This is unambiguous and clearly differentiates it from the list or create-contact/task siblings.

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 tool provides critical usage feedback regarding idempotency: a repeated call with the same parameters will result in a duplicate registration. This helps the agent understand the behavior limits of the tool.

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