get_subscription_upcoming_charges

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

The description specifies the tool returns scheduled charges with amounts and dates, implying a read operation. However, without annotations, it does not explicitly state that it is read-only, nor does it disclose any behavioral traits like idempotency or data freshness constraints.

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 short (two sentences) and front-loaded with the primary purpose. The inclusion of the HTTP path is helpful. However, the fragment 'Optional: include.' feels incomplete and could be integrated more smoothly.

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 low complexity (2 params, no nested objects, no output schema), the description covers the key aspects: what the tool returns and the required input (subscriptionId implied in path). It could mention if only certain subscription statuses are valid, but overall it is adequate.

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 fully describes both parameters, so the description adds no extra meaning beyond the schema. The mention of 'Optional: include' is redundant given the schema already marks include as optional with a description. Baseline 3 is appropriate.

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 'View all upcoming charges for a subscription' with a specific verb and resource. It also mentions the HTTP method and path, which adds context. However, it does not distinguish this tool from related siblings like get_subscription_invoices.

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 provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusion criteria, leaving the agent to infer usage from the name and siblings.

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