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

With no annotations, the description carries the full burden. It discloses behavioral traits such as the token inefficiency warning, the fact that it retrieves from conversation history, and the explicit instruction not to invent or transform the task_id. It adds meaningful context beyond a simple 'read' operation.

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 well-structured with clear sections (Description, Warning, When to use, Args, Returns, Notes). However, the 'Critical Tool Warning' is repetitive and somewhat verbose, using dramatic language like 'severe token inefficiency' and 'extreme token loss', which could be trimmed without losing value.

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?

The description is complete for a tool with no parameters and no output schema. It covers purpose, usage, return values, and important notes about task_id handling. There is no missing information needed for the agent to use the tool correctly.

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, and the description explicitly states 'Args: None', which is clear and sufficient. The baseline for zero-param tools is 4, and the description does not need to add more.

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 clearly states the tool's purpose: 'Retrieve the most recently active coding task UUID (task_id) and metadata from conversation history.' It uses a specific verb and resource, and distinguishes itself from siblings like set_coding_task.

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 explicitly says 'Use when the task_id is missing from context' and provides a 'When to use' section. It gives clear context for when to invoke the tool, though it does not explicitly mention alternatives or exclusions.

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