mcp_opendaw_get_project_metadata

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds the specific return fields (created, bpm, time_signature, etc.), which is useful context beyond annotations. No additional behavioral traits (e.g., performance, side effects) are disclosed, but given the annotation coverage, this is adequate.

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 very concise: three short sentences that front-load the purpose and return fields. No wasted words, though there is slight redundancy between the first and third sentences. Still, it earns its place.

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 simple metadata fetch with zero parameters and an output schema present, the description provides all necessary context: what it returns and that it's a quick overview. No gaps given the tool's simplicity.

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?

There are no parameters, so the description doesn't need to add parameter info. Context notes schema coverage is 100% (trivially) and baseline for 0 params is 4. The description does not add anything beyond what the schema provides, but that's acceptable 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 clearly states it gets project metadata and lists specific fields (creation date, BPM, time signature, AU count, track count). It distinguishes itself as a 'quick overview' but does not explicitly differentiate from siblings like get_project_info or get_full_project_state, thus not a 5.

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 usage for a 'quick overview in one call,' but provides no explicit when-to-use vs alternatives like get_full_project_state or get_project_info. No exclusions or conditions are mentioned.

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