get-subscription

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

Description mentions returned fields (current period start/end, pricing component states) but does not disclose idempotency, error behavior on missing ID, or authentication requirements. With no annotations, this is a moderate gap.

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 well-structured sentences with no unnecessary words. The key information is front-loaded: action, resource, and key result fields.

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 lack of output schema, the description provides reasonable detail about return values (period start/end, pricing states). It could be more exhaustive, but for a simple get operation, it covers the essentials. Error handling 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 covers 100% of parameters and includes a description for subscriptionId. Description does not add any additional meaning beyond what the schema provides, so 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?

Description uses specific verb 'Get detailed state' and resource 'subscription by its unique ID', clearly distinguishing it from sibling tools like create-subscription, cancel-subscription, and list-subscriptions.

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?

Description implies usage when you have a subscription ID, but provides no explicit guidance on when to use vs. alternatives like list-subscriptions or get-customer-summary. No when-not conditions stated.

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