context_status

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

With no annotations, the description carries the full burden of behavioral disclosure. It details what the tool returns, explains the meaning of the phase thresholds, and implies behavior when transcript_path is omitted (defaults to current session). This provides robust transparency beyond the minimal expectations, with no contradictions.

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 concise, front-loading the core purpose in the first sentence, followed by return details and usage guidance. It contains no fluff, and each sentence contributes valuable information, making it efficiently structured for quick comprehension.

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?

Given the tool's moderate complexity with one optional parameter and no output schema, the description is complete. It explains expected return values, provides self-management context, and describes parameter behavior, ensuring an agent has sufficient information to select and invoke 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 schema provides only type and default for transcript_path, with 0% description coverage. The description compensates well by stating it is optional and used 'to target a specific session file,' which clarifies the parameter's purpose and behavior. Minor gaps remain about the exact format or consequences of omission, but the description adds substantial meaning.

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 with a specific verb ('Estimate current context window usage and distance to compaction') and describes the key outputs (phase, token estimates, profile range). It is specific and unambiguous, distinguishing itself from any potential related tools even without sibling context.

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 explains when to use the tool ('Use this to self-manage') and provides actionable thresholds for each phase (open, midstream, narrowing, threshold) with corresponding actions. It also clarifies the optional parameter usage, making it clear when and how to invoke it appropriately.

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