ws_render_template

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

With no annotations provided, the description carries full responsibility for behavioral context. It only states the basic action, omitting details like required auth, rate limits, error handling, or limitations on Jinja2 features. The return value is not described despite an existing output schema.

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 a single 6-word sentence, which is concise but lacks necessary detail. It is front-loaded and has no redundancy, but it is too terse to be fully helpful.

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 the tool's simplicity and the presence of an output schema, the description does not utilize the opportunity to explain WebSocket-specific context (e.g., persistent connection state, lifecycle). It fails to address what the output represents or how errors are surfaced.

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 0%, and the description does not provide any parameter details beyond the schema's name 'template'. There is no explanation of what the template string should contain, expected format, or available variables. The description adds no semantic value.

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 'Render a Jinja2 template via WebSocket', which specifies the verb (render), resource (Jinja2 template), and medium (WebSocket). This distinguishes it from the sibling 'services_render_template' which likely does synchronous rendering.

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. The phrase 'via WebSocket' implies it's for WebSocket-based interactions, but it does not state when a WebSocket render is preferred over the synchronous service or any exclusions.

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