create_score

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

No annotations provided, so description must bear full burden. Describes basic creation behavior and return value, but does not disclose side effects, permissions, or dependencies (e.g., requires Dorico connection). Adequate but not detailed.

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?

Well-structured with Args section and examples, but somewhat lengthy. Every sentence is informative, but could be condensed slightly.

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?

Covers purpose, all 6 parameters, and return value. Mentions output gives score information. Could mention file creation or prerequisite of a Dorico connection, but sufficiently complete for a creation tool.

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?

Adds meaning beyond schema by providing context (e.g., 'score title (shown on first page)') and examples. However, could be more specific about valid instrument names or time signature formats.

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?

Description clearly states the verb 'Create' and the resource 'a new score in Dorico.' It positions itself as the starting point for new compositions, distinguishing it from sibling tools that modify or analyze existing scores.

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?

Explicitly states 'starting point for any new composition,' indicating when to use it. Does not explicitly mention when not to use or alternatives, but sibling tools context suggests this is the only creation tool.

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