get_application_cpu_usage

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Get' implies a read-only operation with no side effects, but the description does not state that explicitly or mention any caveats. For a simple getter, this 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 conveys exactly what the tool does without any unnecessary words or repetition. It is perfectly sized for such a simple operation.

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 the tool's simplicity (no parameters) and the presence of an output schema (which likely documents the return fields), the description is nearly complete. It does not explain what 'average' and 'peak' refer to (e.g., the measuring window), but this is unlikely to mislead an agent.

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 description naturally adds no parameter-level detail. Per the baseline for 0-param tools, a score of 4 is appropriate; the description accurately reflects that no arguments are needed.

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 the action ('Get') and the specific resource ('Ableton application's average and peak CPU usage'). This uniquely distinguishes it from siblings, which are mostly about clips, tracks, devices, or transport.

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?

A clear use case is implied (monitoring CPU usage), but no explicit guidance is given about when to choose this tool over alternatives. Since no sibling tool serves the same purpose, the need for exclusion is low, but a more explicit 'use this when' could improve guidance.

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