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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little: it does not say whether calling it when already connected errors or is a no-op, what happens if the MuseScore plugin is not running, whether it blocks or times out, or whether the connection persists across calls. The only behavioral detail given, the return shape, is already covered by the output schema.

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?

One front-loaded sentence with an explicit action and return shape, no filler. It is efficient, though the return-value clause is redundant with the output schema and could have been spent on connection semantics instead.

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 zero-parameter connection tool with an output schema, the essentials of what it does and what it returns are covered. What is missing is the operational context an agent actually needs: invocation ordering relative to the other MuseScore tools and failure behavior when the plugin is unreachable.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies.

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?

States a concrete verb and resource: opens the WebSocket connection to the MuseScore plugin. It is distinguishable from siblings like ping_musescore or get_score, but does not explicitly contrast itself with ping_musescore, which is the nearest alternative for checking connectivity.

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 this is a connection-establishment step that logically precedes score/cursor operations, but it never says so, nor does it state when to prefer ping_musescore or what to do if a connection already exists. Usage is inferable rather than stated.

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

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

With no annotations, the description carries the full burden; 'Get' reliably implies a read-only operation and the description does enumerate what is retrieved. However, it never mentions that a connected MuseScore instance is presumably required, given the connect_to_musescore sibling, nor any failure behavior without a connection.

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 front-loaded sentence with three concrete returned items and no filler. Every word contributes to identifying the resource.

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?

An output schema exists, so detailed return-value explanation is unnecessary, and a zero-parameter tool needs little schema narration. The only real gap relative to its complexity is the unstated dependency on an active MuseScore session.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. Nothing is misstated or missing on this dimension.

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?

States a specific verb ('Get') and three concrete resources (cursor position, selection, score summary), which makes the output recognizable and distinct from get_score or get_score_metadata. It stops short of explicitly contrasting itself with those siblings.

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?

Usage is only implied: the word 'current' signals this reports live editor state rather than stored score data. There is no explicit statement of when to prefer it over get_score or what preconditions (e.g., an active MuseScore connection) must hold.

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

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.

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

No annotations are supplied, so the description carries the full disclosure burden; it does state the exact scope of data returned, which usefully bounds the operation. It does not state that the call is read-only, whether a connection/session is required, or what happens if no score is loaded — gaps that matter for an unannotated tool.

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 front-loaded sentence with the resource named first and the returned fields parenthesized for scannability. No redundant or filler wording.

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 there is no input complexity to cover. It is nearly complete for a simple read tool; only the connection prerequisite and read-only nature are unstated.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The field list in the description corresponds to output content rather than inputs, which is appropriate here.

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 gives a specific verb ('Get') and resource ('score metadata') and enumerates the fields returned (title, composer, measures, staves, time/key signatures), which makes the scope concrete. The word 'only' implicitly contrasts it with the broader get_score sibling, though it never names that sibling.

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 'only' hints that this is the lightweight alternative when full score content is unnecessary, implying get_score is the heavier option. However, there is no explicit statement of when to prefer this tool, and no mention of prerequisites such as connecting to MuseScore first, which the sibling connect_to_musescore suggests is required.

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

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

With no annotations, the description carries the full load and does disclose non-obvious behavior: the call performs a version handshake, the response includes server and plugin versions, and a false versionsMatch means the plugin is out of sync. It also names the fix command and the required restart steps. It stops short of saying whether the call has side effects or what happens on a failed ping (error vs. a boolean field).

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?

Front-loaded with the one-line purpose, then the handshake detail, then the failure remediation in priority order. Every sentence carries information, though the parenthetical restart sequence is slightly verbose for a description field.

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 no-parameter diagnostic with an output schema, this is nearly complete: purpose, side benefit (version handshake), how to read the key result field, and the recovery procedure. Missing only a note on expected failure modes (e.g., connection refused) and whether it is safe to call repeatedly.

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 nothing for the description to disambiguate — the baseline applies. The description correctly adds no parameter discussion, which is appropriate rather than a gap.

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?

"Ping the MuseScore WebSocket API to check the connection" gives a specific verb (ping) and target (the WebSocket connection) plus the intent (health check). It is clearly distinct from get_score/run_qml, though it never explicitly contrasts itself with the sibling connect_to_musescore, which is the nearest ambiguity.

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?

It states the diagnostic use case and even prescribes remediation when versionsMatch is false, which is real guidance. However it never says when NOT to use it — notably whether connect_to_musescore should be called first when no connection exists — so the agent must infer the ordering.

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

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

With zero annotations, the description carries the full behavioral burden and only partially meets it. It usefully discloses two traits: nesting is permitted exactly one level, and edit actions are wrapped and rolled back per action — but it does not say whether a failing action aborts the whole sequence, whether successful earlier actions persist, whether the call is idempotent, or what authorization/session state is required.

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?

Three short sentences with the envelope shape and the two key behavioral rules front-loaded, no filler. It loses a point because the second sentence outsources essential information to an external document rather than earning its place with self-contained content.

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?

This is a high-complexity tool — 35 action variants, one required parameter, no annotations — and the description is far too thin for it. An output schema exists so return shapes needn't be explained, but the reliance on an out-of-band markdown file leaves an agent unable to determine action semantics, error/rollback boundaries, or cursor-state effects from the definition alone.

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 description coverage is 0%: 35 action variants are enumerated structurally with const discriminators and required fields, but none of the fields are described anywhere. The description only restates the {action, params} envelope and delegates all meaning (pitch, advanceCursorAfterAction, ratio, harmonyType) to docs/ACTIONS.md, so it adds almost nothing beyond the schema's structure.

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?

States a specific verb and resource: processing a sequence of plugin actions, with each entry shaped as {action, params}. This clearly distinguishes it from the single-purpose siblings (ping_musescore, get_score, run_qml) by signaling batched execution, though 'process' is generic enough that the domain (score editing) must be inferred from the action names.

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?

No guidance on when to choose a sequence over calling individual tools, no preconditions (must a score be connected first?), and no exclusions. The only routing information is a pointer to docs/ACTIONS.md, which is an external artifact the agent may not have access to, so it cannot be relied upon as actionable guidance.

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

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

With no annotations supplied, the description carries the full burden and does so thoroughly: undo-step grouping and rollback on error (including nested ctx actions), the setMetaTag/native-write exception, GUI-thread freeze risk from infinite loops, JSON-serializability check before commit, and the allowEval: true prerequisite with its error behavior. It also discloses that the server keeps no state, which is critical for multi-call reasoning.

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 first sentence front-loads purpose and the rest is organized with bullets that map to the mental model an agent needs (ctx/params/state, persistence, constraints). It is dense but nearly every line carries operational consequence; the known-pitfalls doc pointer is the one piece that delegates rather than informs.

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 high-risk eval tool with two parameters, an output schema covering the return value, and no annotations, the description supplies the missing safety envelope, state semantics, and failure modes. Nothing an agent needs in order to call it correctly, or to avoid freezing MuseScore, is absent.

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%, so the description must compensate, and it does: it explains that code is a function body invoked as function(ctx, params, state), enumerates the ctx facade members, clarifies that params is caller-shaped, and warns that state must be mutated rather than reassigned to persist across calls. This adds substantially more meaning than the two bare schema properties provide.

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?

"Execute QML/JavaScript code inside the MuseScore plugin and return its result" names a specific verb (execute), a specific resource (QML/JavaScript code in the plugin), and the outcome (returns result). It is unmistakable against siblings like get_score, ping_musescore, and get_cursor_info, which read state rather than running arbitrary code.

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?

"For complex score tasks that would otherwise need many round trips" gives explicit when-to-use guidance that routes the agent away from piecemeal sibling calls. It also states what is rejected inside a run (playback/mixer actions, undo, recursive eval) and points to get_score before/after for comparisons. It does not explicitly name the sibling tools to use instead for simple tasks, so it stops short of full when-not routing.

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