get_fixture

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

No annotations are provided, so the description carries the full burden; it discloses the returned payload (metadata, DMX addressing, channel definitions, tags), which substitutes for a missing output schema. It does not state read-only nature explicitly, error behavior for an unknown ID, or permission requirements, so it is strong but not complete.

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 with the core purpose, then structured bullets. There is mild redundancy between the 'Returns' list and the 'Use this tool when you need' list, but nothing is wasted enough to hurt clarity.

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-parameter read tool with no output schema, the description supplies the return-field breakdown an agent needs and routes to the correct alternative. Nothing essential to correct invocation 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 description coverage is 100% with a single well-documented fixtureId parameter, so the schema does the heavy lifting. The description adds no format or semantic detail (e.g., accepted ID forms) beyond what the schema provides, so the baseline 3 applies.

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+resource ('Get full details for a specific fixture') and explicitly contrasts scope with the sibling list_fixtures ('basic fixture information'). An agent can distinguish this from the lighter-list tool without opening either schema, though it does not address the overlapping analyze_fixture_capabilities.

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?

Provides explicit when-to-use bullets (complete channel info, capabilities detail, channel types/ranges) plus an explicit when-not/alternative routing to list_fixtures. This is close to ideal routing guidance.

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