get_subscription

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states the basic action (retrieve) without mentioning authentication requirements, rate limits, error behavior (e.g., what happens if ID not found), or any side effects. For a read operation, basic transparency is expected but not met.

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 sentence of 7 words with no fluff. It is front-loaded effectively. However, it is slightly too minimal—adding a brief phrase about return value or common usage would improve without sacrificing conciseness.

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 tool's simplicity (1 parameter, no output schema, no nested objects), the description is minimally adequate. However, it omits any mention of the return value or behavior on missing IDs. Considering sibling tools and the absence of output schema, a bit more completeness would be expected.

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 0% description coverage, and the description only mentions 'by its id' without explaining the format, constraints, or meaning of subscription_id. The schema property lacks a description, so the description should compensate but does not add detail beyond the parameter name.

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 verb 'retrieve' and the resource 'subscription', and specifies retrieval by ID. It distinguishes from list_subscriptions by indicating a single subscription, but does not differentiate from other get_* tools such as get_customer or get_order.

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 on when to use this tool versus alternatives, such as list_subscriptions or other get_* tools. The tool is implied only for cases where a specific subscription ID is known, but no explicit context or exclusions are provided.

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