get_storage_config

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

No annotations are provided, so the description must indicate behavioral traits. The description says 'Get configuration', implying a read-only operation, which is sufficient for a simple retrieval tool. However, it does not mention any authentication requirements, side effects, or rate limits. Given the lack of annotations, the description is minimally adequate.

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 extremely concise with two sentences: one for the tool's purpose and one for the parameter. It is front-loaded with the key action and resource, with no redundant or filler text. Every word contributes meaning.

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 simple retrieval tool with one parameter and an output schema, the description covers the essential (what it does, what input is needed). The existence of an output schema reduces the need to explain return values. However, it slightly lacks context about the typical use case (e.g., configuration vs. status), but remains largely complete for the tool's simplicity.

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 0% description coverage, so the description must compensate. The description defines the 'storage' parameter as 'The storage ID', which adds semantic meaning beyond the raw schema (string type). It clarifies the purpose of the parameter, but does not elaborate on format or constraints (e.g., length, patterns). This partially compensates but remains basic.

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 clearly states the action 'Get configuration' on the resource 'specific storage pool', which is distinct from sibling tools like 'list_storage' (list all) and 'get_storage_rrddata' (time-series data). The verb and resource are specific and unambiguous.

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 usage for retrieving configuration of a single storage pool, but there is no explicit guidance on when to use this tool versus alternatives (e.g., 'list_storage' for enumerating pools or 'get_storage_volume_info' for volume details). No exclusion criteria or prerequisites are mentioned.

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