Delete log stream override

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

Annotations already declare destructiveHint and idempotentHint. The description adds value by specifying the post-deletion behavior (fallback to default workspace log stream) and calls out the exact API call. This goes beyond the annotations, providing useful behavioral context.

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?

Three sentences: action, effect, API call. Front-loaded with key information, no redundant words. Every sentence serves a clear purpose.

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?

The description covers the main effect and API endpoint. No output schema exists, and the description does not mention return type or error cases. However, with annotations (idempotent, destructive) and the simple nature of a delete, it is reasonably complete. Missing explicit idempotency note, but annotation covers it.

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% and already describes the resourceId parameter. The tool description's phrase 'for the specified resource' does not add significant meaning beyond the schema. The schema's parameter description says 'returned' which is slightly off for a delete, but that is a schema issue, not in the tool description.

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 the action ('Delete log stream override') and the resource ('log stream override for the specified resource'), with a specific consequence ('resource will use workspace's default'). This distinguishes it from siblings like render_delete_owner_log_stream and render_update_resource_log_stream. The inclusion of the API endpoint adds further clarity.

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 implies usage by naming the resource and effect, but does not explicitly state when to use this tool versus alternatives (e.g., render_delete_owner_log_stream) or provide prerequisites. The context is clear but no direct guidance on decision-making.

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