get_subscription_rate_plan_charge

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

No annotations provided, but the description includes the HTTP GET method, implying read-only behavior. It does not detail permissions, rate limits, or side effects, but for a simple retrieval, this is adequate.

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?

Two sentences: one describing the function, one providing the endpoint. No unnecessary words, effectively communicates the tool's purpose.

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?

The description is minimal but covers the core function. Without an output schema, it doesn't describe return data, which would be helpful. However, given the tool's simplicity, it is acceptable.

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?

Input schema descriptions cover both parameters (subscriptionId and chargeId) at 100% coverage. The description adds no additional meaning beyond the schema, so 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 the action 'Get' and the resource 'single rate plan charge on a subscription', with the HTTP endpoint detailing the path. It distinguishes from sibling create/update/delete 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 description implicitly indicates use for retrieving a specific charge by ID. While it doesn't explicitly mention alternatives like listing all charges, the context of sibling tools like list_subscription_rate_plans makes it clear.

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