get_subscription

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

No annotations are provided, so the description carries the full burden of behavioral transparency. It does not indicate that the operation is read-only, whether it requires special permissions, or what the response contains. The verb 'get' implies read-only, but that's implicit rather than explicitly disclosed.

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 short sentence, 'Get subscription details,' which is efficient and front-loaded. However, it is minimal and could be slightly more informative without sacrificing conciseness, but it earns its place as a clear and direct statement.

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 absence of annotations and an output schema, the description should explain what the tool returns, any error conditions, or how it relates to other subscription tools. It only states the basic action, which is insufficient for a tool expected to retrieve detailed information.

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 already provides full documentation for the single parameter (subscriptionId with description 'Subscription ID'), giving 100% schema coverage. The description adds no additional parameter semantics, so a baseline score of 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 a verb (get) and resource (subscription details), and it is distinct from sibling tools like create_subscription or update_subscription. However, it lacks specifics about the scope or what exactly 'details' includes, so it doesn't fully differentiate beyond the basic action.

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 provides no guidance on when to use this tool versus alternatives. There are no prerequisites, no mention of search tools, and no context about whether this is for current or historical data. It simply states the action without any usage context.

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