get_storage_partition

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

No annotations exist, so the description must fully disclose behavior. It lists error codes, which is helpful, but does not state read-only nature, return format, pagination, or other behavioral traits. This is insufficient for a tool with no annotations.

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 short and to the point, listing the resource and error codes. It is front-loaded with the main purpose. No redundant or unnecessary sentences.

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 zero parameters and an output schema (likely documenting return structure), the description lacks details on pagination, sorting, or result limits. Error codes are provided, but completeness is moderate for a collection retrieval tool.

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 zero parameters and schema coverage is 100%. There are no parameters to describe, so the description adds no param info, which is acceptable. Baseline 4 is appropriate.

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 it returns the collection of all DiskPartitions. The verb 'Returns' and resource 'collection of all DiskPartition' are specific. However, it does not explicitly differentiate from the sibling `get_storage_partition_id`, though the name implies a list vs. single partition.

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 guidance on when to use this tool versus alternatives (e.g., `get_storage_partition_id`). The description is minimal, providing no prerequisites or context for invocation. A score of 3 reflects the absence of explicit usage advice.

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