Upload photos / carousel

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

Annotations indicate a mutating write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds minimal extra behavior (publishing) but omits traits like asyncUpload defaulting to true, queuing, or scheduling. No contradiction with annotations.

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 at two sentences, front-loading the key purpose and the critical parameter detail. No wasted words.

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's complexity (17 parameters, output schema exists, annotations present), the description is too minimal. It omits important contextual cues about asynchronous behavior, queuing, platform-specific options, and scheduling, leaving significant gaps for the agent.

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 description coverage is 53% (low), but the tool description only adds value for one parameter (photosPathsOrUrls can be URL or local path). Other 16 parameters are not discussed, leaving the agent to rely solely on schema descriptions, which may be insufficient.

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 'Publish one or more photos (single image or carousel)', providing a specific verb and resource. It differentiates from sibling tools like upload_video or upload_text by specifying photos and carousel format.

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?

No explicit guidance on when to use or when not to use this tool vs alternatives. While the sibling list implies other upload tools exist, the description does not help the agent decide between uploading photos, videos, or documents.

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