ableton_get_bridge_observability

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

The word 'Read' implies a non-destructive operation, which is appropriate. However, no mention of required environments, side effects, or authentication needs. Given no annotations, the description carries the burden but only states what it reads, not behavioral nuances.

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?

Single sentence, front-loaded with verb, no filler. Every word serves a purpose.

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?

Adequate for a simple diagnostic read: lists four aspects. But missing details on return format, prerequisites, or when to choose this over other get tools. No output schema to fill gaps.

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 description coverage is only 25%. The description adds context for two parameters (stale-runtime, installedFilePaths) but leaves livePid and lastError unexplained. It partially compensates for low coverage but not fully.

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?

Description starts with verb 'Read' and lists four specific diagnostic areas (bridge version, endpoint support, stale-runtime, installed-file diagnostics), clearly distinguishing it from sibling tools that create, modify, or delete resources.

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?

No explicit guidance on when to use this tool versus alternatives like ableton_get_status. Only implied usage for bridge diagnostics, lacking context on prerequisites or exclusions.

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