Get app output & preview URLs

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds critical behavioral context: client-side rendering and absence of server-side snapshot API. No contradictions.

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?

Two short paragraphs: first gives purpose and a key note, second lists args and returns. No extraneous words, front-loaded with essential info.

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 high schema coverage, good annotations, and no output schema, description covers return fields and a major limitation. Missing error handling or edge cases, but sufficient for a simple read-only retrieval tool.

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%, baseline 3. Description adds value by indicating 'app' is preferred over 'appToken' and briefly restates key args. The preference hint is useful beyond 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?

Description clearly states the tool returns live output URL, broadcast URL, and thumbnail preview from an app instance. Specifies action (return/hand over) and distinguishes from siblings as it's the only tool specifically for output URLs.

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?

Description guides to hand URLs to human or browser renderer to see on-air content, and explicitly notes that Singular renders client-side with no server-side snapshot API, implying when not to use for snapshot needs. No explicit alternative tools mentioned but context is sufficient.

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