chamber_hop_reject_log

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

With no annotations, the description carries the behavioral burden. It does disclose that the log is 'Live' and that 'Extra values never rehydrate', which hints at real-time current data and no enrichment/backfill. However, it never explicitly states that this is a read-only operation or explains what 'rehydrate' means, leaving important behavior ambiguous.

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 very short and front-loads the output format, but the second sentence 'Extra values never rehydrate' is cryptic and costly in clarity. Brevity is achieved at the expense of plain-language comprehensibility, making it appropriately sized but poorly tuned for an AI agent.

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 one-optional-parameter read tool, the description provides the output shape (TSV with three columns) and a limitation. Yet it does not clarify what 'Rider SoT' refers to, what a 'hop-gate reject' is, or how the limit interacts with 'Live', leaving room for misinterpretation.

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 only parameter, limit, is fully described in the schema as 'Max recent entries (optional)', so schema coverage is 100%. The description adds no additional meaning about limit behavior, staying at the baseline 3 because the schema already does the work.

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 names a specific resource (hop-gate reject.log) and the TSV format with columns ISO, code, preview, which distinguishes it from siblings like chamber_status or chamber_hop_gate. However, it lacks an explicit verb such as 'returns' or 'lists', and uses unexplained jargon like 'Rider SoT' and 'rehydrate', so an agent must infer the tool's core function.

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?

No guidance is given on when to use this tool versus chamber_hop_gate, chamber_status, or benefit_check. The phrase 'Rider SoT' hints at authority but does not explain a decision procedure for selecting this tool, and no alternatives or exclusions are mentioned.

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