Get storage info

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, read-only operation. The description adds the specific data returned (endpoints, usage), which is helpful context beyond the annotations. However, it does not disclose any additional behavioral traits such as authentication requirements or rate limits, which the annotations also do not cover.

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?

The description is a single, focused sentence that immediately conveys the tool's purpose. It uses no unnecessary words and is front-loaded with the action and resource.

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 tool with no parameters and no output schema, the description is sufficient: it names the resource and the key data fields (endpoints, usage). The annotations provide safety context. While it could name the return format or distinguish from siblings, the simplicity of the tool makes this adequate.

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 input schema defines zero parameters, so schema coverage is 100% and the baseline is 4. The description adds context that the tool returns account-level endpoints and usage, which clarifies the tool's scope even though no parameters exist.

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 'Get cloud storage account info (endpoints, usage).' This clearly identifies the verb 'get' and the resource 'cloud storage account info,' making the tool's purpose obvious. It distinguishes from sibling tools that target buckets, CDN resources, or external storages, though it does not name them explicitly.

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 implies use for retrieving account-level storage endpoints and usage, but it provides no explicit guidance on when to prefer this tool over alternatives like get_bucket or get_external_storage. There is no mention of excluded scenarios or alternative tools, so the agent must rely on the name alone.

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