get_project_summary

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

No annotations are provided, so the description carries the full burden. It transparently documents the complete return shape, which is the main behavioral information for a getter. It does not explicitly state read-only/no side effects, but 'Get' and the return-only documentation make the read-only nature clear.

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-loads the core purpose in the first sentence, then uses a well-structured Returns list. The length is justified because there is no output schema, though the phrase about giving useful mixing/production advice is slightly editorial rather than strictly necessary.

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, no annotations, and no input parameters, the description fully compensates by enumerating the returned object and all nested track, master, marker, and region fields. Nothing essential for calling or interpreting this summary tool is missing.

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 has zero parameters, so schema semantics are not a concern. Baseline for zero parameters is 4, and the description appropriately does not invent or discuss parameters.

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 ('Get a comprehensive summary of the current REAPER project') and distinguishes itself from sibling getters by being the single-call aggregate that returns project state. An agent can tell it is the high-level summary tool rather than one of the narrow getters like get_project_name or get_tempo.

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?

Clearly indicates the context of use: it returns everything needed to understand project state and give mixing/production advice in a single call. It does not explicitly list when not to use it or name the individual alternatives, but the single-call framing implies preference over multiple narrow getters.

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