ableton_get_project

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

The description clearly labels the operation as a read ('Read'), which implies non-destructive behavior. However, since no annotations are provided, the description carries the full burden. It does not mention any side effects, required permissions, or limits (e.g., performance with large projects). The disclosure is adequate but not rich.

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 concise sentence that efficiently conveys the purpose. It earns its length with specific detail, though it could benefit from a note about output format.

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 the tool has no parameters and no output schema, the description must compensate. It lists what is read but does not describe the structure or format of the returned data. This leaves the agent unsure about how to use the output.

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 (empty input schema), so schema coverage is 100%. According to guidelines, baseline is 4. The description does not need to add parameter details, and it does not attempt to describe nonexistent 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?

The description uses a specific verb ('Read') and resource ('project structure') and lists the components ('tracks, clips, devices, locators, routing, and mixer state'). This clearly distinguishes it from siblings like 'ableton_get_arrangement' or 'ableton_get_status' which focus on different aspects.

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 that this tool is for reading project structure, but it does not explicitly state when to use it versus alternatives (e.g., get_arrangement for arranger view data) or when not to use it. No context-dependent guidance is provided.

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