Import recipe from URL

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

The description adds behavioral context beyond the annotations: it mentions fetching, validation, import process, and constraints like host-allowlisted and size-capped. This supplements the annotations (destructiveHint=true, openWorldHint=true) without contradiction. However, it could elaborate on what 'destructive' entails (e.g., overwriting local files).

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?

A single 20-word sentence that packs the core action, resource, and constraints. Every word earns its place; there is no redundancy.

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 action and key constraints but lacks information about return behavior (e.g., success/failure, imported file paths) and does not explain the validation step. For a tool with no output schema and moderate complexity (4 params), the description is adequate but leaves the agent guessing about post-import state.

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?

All four parameters have detailed schema descriptions (100% coverage). The tool description does not add significant extra meaning beyond synthesizing the parameters' roles (e.g., 'size-capped' ties to max_bytes). With high schema coverage, the description's contribution is marginal.

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 verb (fetch, validate, import), the resource (recipe or recipe-bundle JSON from an HTTPS URL), and the destination (local recipes directory). It also mentions constraints (host-allowlisted, size-capped) that help distinguish from sibling import tools like import_recipe_bundle or import_model.

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 for importing from URLs but does not explicitly state when to use this tool versus alternatives (e.g., import_recipe_bundle for local files, import_model for 3D models). No when-not-to-use or prerequisite guidance is provided, leaving the agent to infer the scope.

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