get_storage

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

No annotations are provided, so the description carries the full burden. It implies a read (verb 'get', plus a 'read-only' token buried in the keyword dump), but it says nothing about the return payload shape, required auth scope, or whether the result is group-scoped or user-scoped. The keyword stuffing is the only behavioral signal offered.

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?

Front-loading is fine (name and endpoint come first), but roughly two-thirds of the text is a redundant keyword blob repeating 'get/fetch/read/retrieve/view/show storage.' That padding dilutes rather than clarifies, which is the opposite of conciseness.

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 annotations, no output schema, and no parameter schema to lean on, the description is the only source of information an agent has, yet it never explains what 'storage' contains or why one would call this. For a no-input discovery tool, that leaves a real gap in deciding whether to invoke it at all.

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 tool takes zero parameters, which is the baseline-4 case. There is nothing for the schema or description to disambiguate, so no deficiency here.

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 is essentially a tautology of the name: 'Get storage' restates 'get_storage' without saying what storage data is returned or what it represents (disk usage, group storage stats, etc.). It does add the routing hint '[GET /api/groups/storage]' and the 'Groups: Self Service' category, but nothing that lets an agent distinguish it semantically from other group-scoped getters like get_group_preferences.

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 among the very large sibling set (get_statistics, get_group_preferences, get_logged_in_user_group, etc.). The keyword list ('get storage, fetch storage, read storage...') is synonym padding, not usage guidance.

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