telos.rendering.capabilities

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

Discloses read-only, zero-auth, and no external side effects directly in description, compensating for absent annotations. Also mentions return format (JSON renderer capability contract).

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 sentences with zero waste. First sentence front-loads usage purpose, second covers behavioral transparency and output. Every sentence earns its place.

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 zero parameters, no output schema, and simple purpose, the description fully covers what the tool does, its side-effect profile, and return type. No gaps remain.

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?

No parameters exist (schema coverage 100%), so baseline 4 applies. Description adds value by explaining the return value type and purpose, which is meaningful beyond the empty 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?

Clearly states the tool is used to choose rendering fallbacks (WebGPU, WebGL, canvas, static) for Studio surfaces. Distinguishes from sibling 'telos.rendering.research' by focus on capability contract vs. research.

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?

Explicitly states when to use: 'Use when a host must choose...fallbacks'. Provides clear context for usage without needing exclusions or alternatives beyond sibling list.

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