Register Newsletter Asset

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds behavioral nuance by explaining that the tool reuses hosted URLs without uploading bytes, which aligns with the annotations and provides extra context.

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 extremely concise—only two sentences. It is front-loaded with the main action and scope, with 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 the tool has an output schema (not shown) and moderate complexity (4 params, 1 required), the description is complete. It covers the purpose, input requirements (hosted URL), and behavior (no re-upload). No gaps.

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 schema already documents each parameter. The description does not add significant meaning beyond the schema; it primarily reinforces the URL registration aspect. Baseline 3 is appropriate.

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 action ('Register'), the resource ('Shipmail-hosted image or video URL'), and the objective ('as a reusable newsletter asset, without re-uploading bytes'). It distinguishes itself from other newsletter tools by highlighting the reuse of hosted URLs.

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 provides clear context for when to use the tool (reusing hosted media) but does not explicitly exclude other scenarios or mention alternatives. However, the context of 'without re-uploading' effectively guides usage.

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