get_tracked_item

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds a small but useful behavioral detail with '(if any)', indicating that the result may be empty when no task is being tracked. This is modest extra context beyond the annotations, not a rich behavioral disclosure.

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 a single sentence with no wasted words. It front-loads the core action and resource, and the parenthetical '(if any)' adds necessary optionality information without bloating the description.

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 zero-parameter, read-only tool with an output schema and readOnlyHint annotation, the description fully satisfies the agent's needs. It clearly states what the tool returns and the optional nature of the result. No additional context about return values is required because an output schema exists.

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?

The tool has zero parameters, so there are no parameter semantics to document. The schema coverage is effectively 100% because the input schema is empty, and the description correctly focuses on output rather than input. The baseline of 4 applies here since no parameter explanation is needed.

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 uses a specific verb ('Show') and a precise resource ('which task is currently being time-tracked'), which makes the tool's purpose immediately clear. It also naturally distinguishes it from related siblings like get_time_tracks by emphasizing the current active tracking state rather than a history of tracks.

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 phrase 'currently being time-tracked (if any)' clearly signals the intended use case: check the active tracking state. It does not explicitly mention alternatives or exclusions, but the 'current' qualifier is enough context to prevent obvious confusion with time-tracking history tools.

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