get_ableton_logs

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

With no annotations, the description carries the load and does well: it discloses the side effect (local file read, no Live contact) and the edge case (diagnostic string when no log is found). It omits permission requirements and any bound on read size beyond the example.

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-loaded purpose, then side effects, a concrete example, and edge cases. Four short lines with zero filler; every sentence adds usable information.

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 single-optional-param, read-only diagnostic tool with an output schema already covering the return shape, the description supplies purpose, side effects, usage example, and failure behavior. Nothing needed to invoke it correctly 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?

Schema coverage is 0% and the lone 'lines' parameter is undocumented in the schema, but the example get_ableton_logs(50) -> last fifty lines clearly conveys the parameter's meaning and unit. The default of 100 is only in the schema.

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 (read the tail of the newest Ableton Log.txt) with a Windows platform scope. It also distinguishes itself from every sibling by clarifying it operates on a local file rather than the Live session.

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 'does not contact Live' note implies diagnostics use, but no explicit when-to-use condition or named alternative is given. An agent must infer that this is the fallback when the bridge/session tools fail.

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