inspect_clip_groove_postconditions

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is known. The description adds valuable context: it clarifies this tool does not execute actions, prove provenance, or validate audible equivalence, and it explains operation-specific expectations (appended groove vs. removed assignment). This goes beyond annotations without contradicting them.

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 sentences, front-loaded with purpose and scope, followed by exclusions and expectations. Every sentence adds value with no redundancy or fluff.

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 verification tool with no output schema, the description explains what it checks and operation-specific criteria but does not describe the return format or how results are presented. This is a moderate gap given the tool's complexity and the lack of an output schema.

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 coverage is 75% (trackId, clipId, before are described; operation only has enum). The description adds minimal parameter semantics beyond the schema, mainly clarifying that 'before' is a snapshot from get_clip_groove_context. With high schema coverage, the baseline of 3 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 states a specific verb ('Read' and 'inspect') and resource ('native context', 'extraction or baking postconditions') with a precise scope. It explicitly names what it does not do ('Does not execute the UI action, prove provenance, or validate audible equivalence'), which differentiates it from related tools like get_clip_groove_context.

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 clearly implies usage after a bake/extract operation by referencing a 'pre-action get_clip_groove_context snapshot' and defining expected outcomes per operation. However, it does not explicitly state when not to use it or name alternative verification tools, leaving some inference to the agent.

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