get_measure_content

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

No annotations provided, so the description carries the burden. It states 'Read' (non-destructive) and mentions limited data for Dorico/Sibelius. However, it does not disclose error behavior, return format, or valid ranges for parameters, leaving gaps.

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 concise: two sentences and a parameter list. Every sentence earns its place, and the purpose is front-loaded. No redundant information.

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 has an output schema, return values need not be explained. However, the description lacks information on error handling, valid ranges, or what 'content' constitutes (e.g., notes, rests). For a simple read tool, it is minimally adequate but could be more complete.

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 0%, but the description adds indexing conventions: 'measure: Measure number (1-indexed)' and 'staff: Staff index (0-indexed, default: 0)'. This adds meaning beyond the schema types and defaults.

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 'Read the content of a specific measure and staff', which distinguishes it from sibling tools like 'read_passage' or 'get_live_score_info'. The verb 'Read' and resource 'measure and staff' are specific and match the tool name.

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 mentions compatibility (MuseScore best, others limited) but does not explicitly state when to use this tool vs alternatives like 'read_passage' or 'get_selection_properties'. No when-not or exclusion criteria provided.

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