upload_image_and_embed

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

With no annotations, the description carries the burden of behavioral disclosure. It transparently explains input precedence (image_base64 ignored if input_file is provided), auto-detection of filename/content_type, and the side effect of replace_url on the page body. It does not mention permissions or rate limits, but it discloses the key mutation behavior and parameter interactions.

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 compact and front-loaded with the core purpose in the first sentence. The Args list is structured and every line adds value, with no filler or repetition of schema constraints. It earns its length for a 6-parameter tool.

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?

For a 6-parameter mutation tool with no annotations, the description covers purpose, all parameter semantics, input methods, and side effects. An output schema exists, so return values do not need description. The only minor gap is lack of explicit sibling differentiation, but that is not central to completeness.

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?

The schema has 0% description coverage, so the description fully compensates by explaining all six parameters in the Args section. It adds meaningful context: page_id is the page ID, image_base64 is ignored when input_file is set, content_type auto-detects from filename, and replace_url swaps external URLs. This goes far beyond the bare schema property names.

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 opens with a clear verb+resource: 'Upload an image and optionally embed it in the page.' This distinguishes it from sibling tools like upload_attachment, which likely only uploads, by explicitly mentioning the embedding capability. The two input modes (file/base64) add specificity.

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 conveys clear context for when to use the tool: uploading an image and optionally embedding it, with an explicit use case for replace_url (replacing an external image URL). However, it does not explicitly name alternatives or state when not to use it, such as recommending upload_attachment for plain uploads, so it stops short of full exclusion guidance.

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