Get project

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value beyond annotations by specifying the exact content of the returned project and asserting its authoritative nature, which helps the agent understand the scope and reliability of the response. No contradiction with annotations.

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 a single, information-dense sentence. It lists all relevant components without any filler or redundancy, earning a top score for conciseness.

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 that this is a project-wide getter with no output schema, the description provides a complete inventory of what the agent can expect. It is sufficiently detailed for an agent to decide when and how to invoke the tool, especially with the clear sibling contrast.

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, and the schema's properties object is empty, so the description correctly omits parameter details. With no parameters, the baseline is 4.

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 uses the specific verb 'Return' and names the resource as 'the authoritative DAW project.' It enumerates the included components (transport, tracks, steps, clips, mixer, effects, plugins, EQ, automation), which clearly differentiates it from sibling tools that each modify a single component.

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 'authoritative' implies this is the canonical read for the full project state, and sibling tools are all mutations or targeted updates, making the usage context clear. However, it does not explicitly state 'when not to use' or name an alternative, so it misses the bar for a 5.

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