subscriptions_get_raw_by_short_uuid

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally, but the description adds nothing beyond that: no return shape, no note on how 'raw' data differs from a normal subscription fetch, no output schema to fall back on.

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 that brevity is under-specification rather than conciseness. The single clause duplicates the tool name and carries no additional payload for the reader.

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 read tool with no output schema and completely undocumented parameters, the description does not supply what the structured fields omit. The key ambiguity, what 'Raw' returns versus the plain get, is left unexplained.

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 two parameters. The description says nothing about the format of shortUuid or what withDisabledHosts does (it is oddly typed as a string with default 'false'), so the agent must guess at both the identifier shape and the flag's effect.

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 merely restates the tool name: 'Get' + 'Raw Subscription' + 'by Short UUID'. It adds no information about what 'Raw' means or how this differs from the sibling subscriptions_get_by_short_uuid, which appears to differ only by that qualifier.

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?

No when-to-use guidance, no alternatives named, and no distinction drawn from the three other subscription retrieval siblings (by user id, by username, raw vs non-raw). The agent is left to infer selection from the name alone.

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