pool_get

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

No annotations provided; description adds '[READ]' to indicate non-destructive operation and mentions configuration dependency. Lacks details on error handling or side effects, but adequate for a simple read tool.

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?

Extremely concise: 4 lines with clear header and bullet-point arguments. No wasted words, every sentence adds value.

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?

Covers core functionality and parameter usage well. Lacks explicit return format but acceptable given no output schema. Slightly more detail on what 'detail' includes would improve 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?

Schema description coverage is 0%, but description fully explains both parameters: pool_id reference to pool_list for valid UUIDs, target as optional config name with default. Adds essential meaning beyond 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?

Explicitly states 'Detail for one pool by uuid.' Clearly specifies verb (READ/detail), resource (pool), and identifier (uuid). Differentiates from pool_list (list all) and pool_patch_ha_posture (patch HA posture).

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?

Provides clear guidance on parameters: pool_id should come from pool_list, target is optional with default. Does not explicitly exclude other tools but context is clear for this read operation.

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