create_eventsource

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

Annotations already mark readOnlyHint=false, and the description adds 'requires write permission' plus the format expectation (same as export_eventsource output). This supplements the safety profile without contradicting annotations. It does not disclose the overwrite deletion behavior, but that is covered by the 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?

Two sentences with zero waste. The core action and format are front-loaded, and the alternative is stated concisely. Ideal length for the information provided.

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?

Covers the essential creation intent, format, and permission. However, it omits any mention of the response or success behavior (e.g., whether the created EventSource is returned), which is left ambiguous given no output schema. For a creation tool, this is a moderate gap.

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%, so the baseline is 3. The description adds value by clarifying that 'definition' must be in REST API format (matching export_eventsource output), which is a semantic detail not in the schema. This helps the agent format the parameter correctly.

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?

States a specific verb (Create), resource (EventSource), and method (via REST API). Clearly distinguishes from import_eventsource by format, preventing confusion. The phrase 'from a full definition dict' further specifies the input requirement.

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 names the alternative tool (import_eventsource) and the condition that selects it (LM Exchange format). Also mentions the write-permission prerequisite, giving clear when-to-use context.

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