getTimeEntry

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

The annotations declare readOnlyHint=true, so the agent knows this is a read-only operation. However, the description adds no behavioral context beyond that—no mention of required timeEntryId, return format, or any side effects. It adds zero value beyond the annotation.

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 extremely concise (five words), but it is under-specified. It lacks essential information about parameters and usage. This is not effective conciseness; it is a failure to provide necessary context. The structure is minimal but not informative.

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 simple get tool with two required parameters and no output schema, the description should at least mention that it retrieves a single time entry by ID. It does not. The tool has moderate complexity due to nested pathParams, but the description provides almost no contextual detail, leaving the agent to rely solely on the schema.

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 0%, so the description must compensate by explaining parameters, but it does not. The description 'Show time entry' does not mention that timeEntryId is required, nor does it clarify the format parameter. An agent cannot infer parameter meaning from this description.

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 'Show time entry' clearly identifies the action (show) and resource (time entry), so an agent understands it retrieves a time entry. However, it does not differentiate from the sibling getTimeEntries, which likely retrieves a list. The clarity is adequate but lacks explicit distinction from similar tools.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it is for a single time entry by ID, nor does it exclude contexts where getTimeEntries or other tools should be used. There is no context or alternatives provided.

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