get_score

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

No annotations are supplied, so the description carries the burden of behavioral disclosure. It does convey the return payload scope well, but it omits traits that matter for a full-score dump: potential response size across all measures/staves/notes, whether a score must already be open or connected, and whether the call is read-only (only implied by the verb "Get").

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?

A single sentence with the action front-loaded and the payload scoped in a compact parenthetical. Nothing is redundant and nothing could be trimmed without losing 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?

With an output schema present, the description need not explain return values, and with zero parameters the schema burden is nil, so the definition is close to complete. The remaining gap is routing: the reader is not told how this differs from get_score_metadata or what preconditions (e.g. an active connection) apply.

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 zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description does not confuse matters by implying hidden inputs, and the empty schema is consistent with the stated behavior.

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?

"Get the full score analysis" pairs a specific verb with a specific resource and enumerates the returned contents (metadata, measures, staves, notes, harmonies). It is clear what the tool does, but it does not explicitly distinguish itself from the sibling get_score_metadata, whose name overlaps with the first item in the list.

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 word "full" implies this is the heavyweight, return-everything option, which implicitly contrasts with get_score_metadata, but no when-to-use or when-not-to-use condition is stated. An agent must infer that this is the right choice when it needs more than metadata, and must infer the cost of a full dump.

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