edit_stream

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

No annotations provided, so description carries full burden. Discloses that the slug/id is immutable—a key behavioral trait. However, does not mention other behaviors like reversibility, permissions, or side effects. Adequate but not comprehensive.

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 plus a concise args list. Front-loaded with the main purpose, no extraneous words. Every sentence adds value.

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 low parameter count and absence of nested objects, the description covers necessary info. Includes immutability note and clarifies parameter sources. Output schema exists but not needed for understanding. Lacks usage context but otherwise complete.

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 0% with only basic property names. The description adds essential meaning: explains that 'stream' is the id from list_streams, 'name' is optional new display name, and 'purpose' is optional enduring purpose. Greatly enhances understanding beyond the 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 renames or repurposes a stream, with specific verb+resource. Distinguishes from siblings like create_stream and remove_stream by focusing on modifications, and notes the id is immutable, adding 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?

Context is clear: use when you need to change display name or purpose of an existing stream. Lacks explicit when-not or alternatives, but the purpose is straightforward and the sibling list provides implicit differentiation.

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