ebill_status

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

With no annotations, the description carries the full burden. It mentions a 'logged-in eBill window' implying an existing session, but doesn't disclose side effects, what 'reachable' means, error conditions, or whether the result includes additional data. The terseness limits transparency.

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 concise sentence that front-loads the core function. It has no filler words, and each element (reachability, session time left) is relevant and contributes to understanding.

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 status tool, the description covers the primary output concept (reachability and remaining session time). However, it lacks context about what 'reachable' means, the expected return format, and any system prerequisites. It's minimally adequate but leaves some gaps.

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 input schema has zero parameters, so there are no parameter semantics to explain. Baseline of 4 applies due to the zero-parameter case, and the description doesn't need to add parameter details.

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 assesses 'whether a logged-in eBill window is reachable, and how long the session has left.' This identifies a status-checking function distinct from siblings like ebill_open or ebill_get_bill. Although it lacks an explicit verb, the implication of 'whether' conveys a checking/reporting operation.

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 compared to siblings such as ebill_open or ebill_list_bills. It doesn't mention prerequisites, ideal contexts, or any exclusions, leaving the agent without direction on when it is appropriate.

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