create_recipes_create_html_or_json_stream

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

The description mentions streaming via SSE but omits critical behavioral details such as response format, error handling, authentication requirements, rate limits, or event schema. With no annotations, the agent has minimal insight into the tool's behavior.

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 concise sentence (20 words) but lacks structure like bullet points or sections. It is easy to read but could benefit from clearer formatting for scanning.

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 5 parameters, no output schema, and no annotations, the description is too brief. It fails to describe return values, streaming event details, error states, or prerequisites, making it incomplete for an agent to use effectively.

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%, so description should explain parameters. Only 'data' is mentioned (as raw HTML or JSON). Parameters 'url', 'includeTags', 'accept-language', and 'includeCategories' are not explained, leaving the agent without guidance on their purpose or expected values.

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 it takes raw HTML or a JSON string of a Recipe object and parses it into a recipe with streaming progress via SSE. It distinguishes from siblings like create_recipes_create_html_or_json (non-stream) and create_recipes_create_url_stream (URL-based streaming).

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 the streaming use case but does not explicitly state when to use this over alternatives like create_recipes_create_html_or_json (non-stream) or create_recipes_create_url_stream (URL-based). No when-not-to-use or alternative guidance is provided.

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