get_score_overview

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost none of it: no statement that the call is read-only and side-effect free, no cost or size expectations, no indication of which score is inspected given the tool takes zero arguments. The only behavioral content is a sketch of the returned hierarchy, delivered parenthetically rather than as an explicit contract.

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?

Two short clauses with no filler, and the resource inventory comes first. The parenthetical '(voice-stream id -> instrument, staff index, voice index)' is dense and slightly cryptic in its arrow notation, which costs a point on readability but not on economy.

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?

With no output schema and no annotations, the description is the sole source of return-value information, and it covers the hierarchy but not the actual field names, ordering, or how a zero-argument call resolves which score is inspected. Adequate as a mental model, insufficient as a contract for a tool whose entire value is its return payload.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. It does not waste space restating an empty schema.

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 enumerates exactly what the tool surfaces: players, instruments, layouts, flows, and per-flow streams and voices with instrument, staff index, and voice index. That is a specific, structural picture of the resource that an agent can distinguish from sibling tools like read_music. It loses a point only because no explicit verb frames it as a retrieval of the current score's structure (the verb is carried entirely by the 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?

'Use the voice ids for read_music/add_notes' gives downstream usage guidance, implying this is a discovery step before note-level operations. However, it never states when to prefer this over siblings such as get_bar_map, get_selection, or read_music, nor any exclusion or prerequisite ordering.

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