get_beat_repeat_performance_context

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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds meaningful behavioral context: it clarifies that Grid/Interval labels are native integers, duplicate labels are not assumed equivalent, and quantized behavior is not inferred from the mapping. It also states 'no audible outcome is inferred', which goes beyond the annotation to explain interpretation constraints.

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 a single, well-structured paragraph. The main content (what is read) is front-loaded, followed by a clarifying note on label interpretation and a read-only reminder. Every sentence adds value, though the mapping caveat is quite technical and could be seen as dense. Still, no 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?

The description comprehensively enumerates the snapshot contents (Repeat, Grid, Interval, Block Triplets, Mix Type, all exposed parameters, track routing, monitoring, transport) and adds a crucial caveat about label interpretation. Without an output schema, this gives a good indication of what will be returned. It does not describe error conditions or the exact response structure, but this is acceptable given the tool's scope.

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?

Both parameters (trackId, deviceId) are fully documented in the schema with clear descriptions ('Stable device-owner ID...', 'Stable device ID...'). The description does not add any new parameter semantics beyond the schema, so the baseline of 3 applies given 100% schema coverage.

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 clear verb ('Read') and a specific resource ('one native snapshot of a loaded Beat Repeat's...'), listing the exact set of fields (Repeat, Grid, Interval, etc.). This immediately distinguishes it from write tools like 'set_beat_repeat_grid' and from similar read tools like 'get_looper_performance_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 implies its use case (inspecting Beat Repeat state) and emphasizes read-only behavior, but does not explicitly mention when to use it over alternatives such as 'get_device_hierarchy' or 'list_device_parameters'. The name itself provides some differentiation, but there is no direct 'use this when' or 'instead of' guidance.

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