clockodo_get_entry

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

Annotations already declare readOnlyHint=true, so the description's job is lighter. It adds value by mentioning the deactivated flag, but it does not disclose behavior on missing ids, error responses, or whether soft-deleted entries are included. This is acceptable but not rich.

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?

One compact sentence carries the core purpose plus a relevant return detail. There is no filler, and the key scoping information ('single time entry by id') is front-loaded.

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 one-parameter read-only fetch tool, the description covers the essential purpose and the notable return flag. No output schema exists, but the lack of detailed return documentation is less critical for such a simple get operation.

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% and the only parameter, id, is already described as 'entry id'. The description confirms id is the selection key but adds no additional format, constraints, or meaning 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 states a specific verb ('Fetches'), a specific resource ('a single time entry'), and a distinguishing detail (includes 'its deactivated flag'). It clearly differentiates from sibling list tools like clockodo_list_entries, which fetch multiple entries.

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 makes the tool's use case clear: fetch one specific time entry by id. It does not explicitly name an alternative or exclusion condition, but the sibling set makes it evident that list_entries is for broader queries and create/update/delete are for mutations.

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