get_groove_pool

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

With no annotations, the description carries the burden. It transparently states the tool returns a list and lists the exact fields included. As a read-only getter, this fully discloses the expected output and implies no side effects, which is sufficient for this simple operation.

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 short sentences, with the primary action stated in the first sentence and supplementary return-value detail in the second. Every word earns its place; no fluff or repetition.

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 tool's simplicity, zero parameters, and the presence of an output schema, the description adds valuable context by listing the fields in the returned list. It fully covers what the agent needs to know to select and invoke this tool correctly.

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 tool has zero parameters, so the baseline is 4. The description additionally explains what the return value contains, which is more relevant than parameter details here. Schema coverage is 100% by virtue of an empty properties object, so no parameter explanation is needed.

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 tool retrieves all grooves from the groove pool and enumerates the returned attributes (index, name, base subdivision, etc.). This specific verb+resource combination distinguishes it from sibling tools like get_groove_properties, which presumably targets a single groove.

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 establishes clear context: it is a no-parameter retrieval of the entire groove pool. While it does not explicitly compare alternatives, the 'all grooves' phrasing makes the use case obvious, and the zero-parameter schema reinforces that this is meant for full-list retrieval.

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