Log time

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/no-idempotency profile is covered structurally. The description usefully adds that a new entry is created and returns an id, which implies repeat calls create duplicates, but it says nothing about permissions or duplicate-submission risk.

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?

Two sentences, zero filler, with the action front-loaded and the return value second. Nothing could be trimmed without losing information.

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?

For a mutation with no output schema, it at least tells the agent what comes back (the created entry and its id). With fully documented params and annotation-covered safety, the only real gap is the one-of issue_id/project_id requirement and non-idempotent duplication behavior.

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 100%, so all six parameters (hours, comments, issue_id, project_id, spent_on, activity_id) already carry their own descriptions and defaults. The description adds no formatting, validation, or mutually-exclusive-field detail beyond that baseline.

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?

States a specific verb and resource ('Logs time on an issue or a project') and adds the outcome ('Returns the created entry (with its id)'), which cleanly separates it from time_list_entries and time_update_entry. It never names a sibling or explicit boundary, so it stops short of a 5.

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 when-to-use guidance, no mention of alternatives like time_update_entry or time_delete_entry, and no prerequisites. The critical constraint that exactly one of issue_id or project_id must be supplied is only discoverable in the schema, not the description.

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