get_storage_disk_id

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

Since no annotations are provided, the description must carry full behavioral disclosure. It only states it returns a StorageDisk and lists error codes, but does not describe side effects, authentication needs, or what the return value includes. Minimal beyond purpose.

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 two sentences: the first clearly states the function, and the second lists error codes. It is concise and front-loaded, though the error list could be more structured.

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?

Given the existence of an output schema, the description need not detail return values. However, it lacks information about prerequisites (e.g., valid id) and does not explain how this tool fits with siblings like 'get_storage_disk'. Error codes are helpful but insufficient for completeness.

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 has one parameter 'id' (string) with no description, and the tool description does not explain what the id represents or its expected format. Schema coverage is 0%, and the description adds nothing beyond the schema.

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 uses the verb 'Returns' and specifies the resource 'StorageDisk' with the given id. It distinguishes from siblings like 'get_storage_disk' (likely returns all) and 'put_storage_disk_id' (updates), making the purpose clear.

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 explicit guidance on when to use this tool versus alternatives. The error codes hint at failure conditions but do not provide context for when to prefer this over sibling get tools.

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