get_groove_properties

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Get detailed properties' without stating whether the operation is read-only, what happens if the groove_index is invalid, or which specific properties are returned. This is minimal disclosure.

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: a one-sentence purpose and a single argument definition. It is front-loaded with the action and avoids any unnecessary words 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 existence of an output schema, return values are presumably defined there. The description covers the essential input parameter but provides no context about the groove pool, prerequisites, edge cases, or related tools. For a simple getter with one parameter, it is adequate but minimal.

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 schema provides only the title 'Groove Index' with no description. The description adds 'Zero-based index of the groove in the groove pool,' which gives meaningful context about the indexing and the target object. However, it does not elaborate on valid ranges or potential errors, so it is adequate but not exceptional.

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 'Get detailed properties of a specific groove,' which is a specific verb+resource. It distinguishes from siblings like get_groove_pool (which retrieves the entire pool) and set_groove_property (which modifies a property). The args clarify the index-based access to 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 provides no guidance on when to use this tool versus alternatives. It does not mention situations where get_groove_pool would be more appropriate or how it relates to other groove-related tools. There is no explicit 'use this when' or exclusions.

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