Retrieve a subscription

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no error/not-found behavior, no note on whether the subscription is returned live or cached, no auth expectations.

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?

It is short, but the second sentence repeats the first almost verbatim, so the only new information is the `sbs_…` prefix, which is already in the schema. Two sentences where one would have done.

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 single-parameter read-only getter with full annotation coverage, complete schema documentation, and no output schema, very little is required of the description. It would be improved by noting not-found behavior, but nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100% and the single `id` parameter is documented with the same `sbs_…` format hint. The description repeats rather than extends the schema, so the baseline of 3 is correct.

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?

It says 'Retrieve a subscription by id' — a verb plus resource, and the `sbs_…` prefix signals the id namespace. However, it largely restates the name and title, and gives no way to distinguish it from siblings such as list_subscriptions or get_subaccount beyond the obvious read-one-vs-list-many distinction the name already implies.

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?

There is no when-to-use guidance at all: no statement of when a single-subscription fetch is appropriate versus list_subscriptions or get_customer, no prerequisites, and no mention of what to do when the id is unknown.

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