project_get_metadata

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

Despite no annotations, the description discloses a major behavioral limitation: the API only exposes which fields are set, not their values, and explicitly notes values are write-only. It also explains the exact return structure (fields_set and tags_present) with an example, even specifying the REAPER version verified. This exceeds expectations.

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 efficiently structured: a one-sentence purpose, a brief context paragraph, and a crucial note on API limitations. Every sentence adds value, and the most important behavioral warning is clearly separated. No redundancy or fluff.

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 getter with no output schema, the description is fully complete. It covers what the tool does, where it fits in REAPER, what it returns (fields_set and tags_present with examples), and its key limitation. An agent has all necessary information to invoke and interpret the result.

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 the baseline of 4 applies. The description adds no param details needed, but it does clarify the return payload, which indirectly helps an agent understand there are no inputs required.

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 starts with a clear, specific verb phrase: 'Get project render metadata' and lists example fields (title, author, album, comment). This distinguishes it from sibling tools like project_get_info (project properties) and project_set_metadata (the setter counterpart).

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 gives clear context by explaining these are fields REAPER embeds into rendered files and how they're used in filename templates, as well as where they appear in the GUI. It implicitly signals when to use this tool, though it doesn't explicitly name alternative tools like project_get_info or project_get_notes for exclusion.

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