subscriptions_get_raw_subscription_by_short_uuid

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

No annotations exist, so the description carries the full behavioral burden. It discloses almost nothing: 'Tags: [Protected]' hints at auth requirements, but there is no statement about rate limits, what the 'raw' payload format is, or how it differs from the non-raw endpoint.

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 and front-loads the endpoint, but the content is an unfiltered spec dump rather than deliberately economical prose; nearly every line is redundant restatement of the name.

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?

With no output schema, no annotations, and two undocumented parameters (one wholly mysterious), the description should explain what 'raw' returns and what withDisabledHosts does, but it leaves both unanswered.

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 both parameters. The path template implies shortUuid identifies the subscription, but withDisabledHosts is completely unexplained in both the schema and the description, so the description fails to compensate for the coverage gap.

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 title restates a specific verb and resource ('Get Raw Subscription by Short UUID'), so an agent knows it fetches a subscription. However, 'raw' is never defined, and there are several near-identical siblings (subscriptions_get_subscription_by_short_uuid_protected, subscription_get_subscription_info_by_short_uuid) that the description does nothing to distinguish from.

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 is a bare endpoint dump with no when-to-use guidance, no prerequisites, and no mention of the closely related siblings that would let an agent choose between them.

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