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

Annotations are empty, so the description carries the full behavioral burden. It declares the operation is a read, explains that pending orders defer charging until assignment, and describes the per-phone monthly renewal cycle. This gives an agent an accurate model of side effects and internal billing semantics, though it stops short of mentioning authentication requirements or failure behavior.

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?

Three sentences with no wasted words: the first gives the summary, the second explains the billing model required to interpret the result, and the third supplies the usage directive. Information is front-loaded and each clause earns its place.

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 parameterless read tool with no output schema, this description covers the essential return semantics (phone count, cost, renewal dates, pending orders) and the special billing model (separate monthly cycles, deferred first-month charge). Nothing critical is missing for an agent to invoke and interpret 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?

There are zero parameters, so the baseline is 4. The description provides no parameter documentation because none is needed, but it compensates by explaining the shape and meaning of the returned data (`lines` and `pending_orders`), which is the only semantic information an agent needs.

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 opens with a specific verb ('Read'), a precise resource ('the authenticated user's phone rentals'), and enumerates concrete outputs: device count, cost, renewal dates, and unassigned orders. It also clarifies the conceptual model (per-phone subscriptions, pending orders), making it clearly distinguishable from sibling tools.

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 closing instruction, 'Start here before proposing any billing change,' explicitly tells an agent when to call this tool first. It does not enumerate exclusions or compare directly with get-billing-request-tool, but the contextual guidance is clear enough for the main use case.

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