Astra: show a target in the app

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

Beyond annotations, the description discloses that the window is brought to front, that playback is not started, that refs can go stale and return 404, and that refs should never be parsed or edited. This adds significant behavioral context not captured by the annotations.

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 front-loaded with the main purpose and stays concise. All sentences serve a purpose—covering behavior, parameter handling, and error cases. No redundancy or fluff.

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 this is a simple navigation tool with one parameter and no output schema, the description covers all essential aspects: what it does, what it doesn't do, how to handle the parameter, and a potential error case. It is contextually complete for an agent to use it correctly.

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 100%, including a detailed description of targetRef. The tool description adds extra guidance about passing refs verbatim and the risk of staleness, which is valuable beyond the schema. Baseline 3 raised due to this additional semantic guidance.

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 a specific action: 'Bring the Astra window to the front and navigate to a track, album, artist, or playlist.' It also distinguishes from siblings by noting 'it does not start playback,' setting it apart from playback tools like astra_play.

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 provides context for when to use the tool: to show a target without starting playback. It explicitly states it takes a ref from astra_search, which implies a prerequisite. However, it doesn't explicitly name alternative tools or when-not-to-use exclusions beyond playback.

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