subscription_info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds nothing on top of that - no auth requirements, no rate limits, no indication of whether this hits a public or admin endpoint, and no note about caching or freshness. For a bare read tool the annotations carry the safety profile, but the description contributes no additional behavioral context.

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?

A single, front-loaded fragment with no wasted words. It is efficient, though so terse that it leaves the reader without critical context.

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 lookup tool with no output schema and an undocumented parameter, the description should clarify what 'info' means (subscription URL, status, traffic, expiry) and which endpoint family this belongs to. None of that is present, so an agent has to guess at the return shape.

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 description coverage is 0% for the single required parameter. The description only repeats the parameter's intent ('by Short UUID'), which the schema property name shortUuid already conveys, and gives no format, length, or validation details for the UUID.

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 states a verb ('Get') and a resource ('Subscription Info') plus the lookup key ('by Short UUID'), so the basic operation is identifiable. However, 'Subscription Info' is vague about what is actually returned, and the sibling list contains near-identical names (subscriptions_get_by_short_uuid, subscription_request_history_list) with no differentiation offered.

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, no prerequisites, and no mention of alternatives. An agent cannot tell from the description whether this is the right tool versus subscriptions_get_by_short_uuid or subscriptions_get_raw_by_short_uuid.

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