foto_publish_series

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

With no annotations, the description carries the full burden. It does disclose that dryRun validates without uploading (and the schema adds that it skips login), but it never states that a real run publishes publicly, whether the action is reversible or editable afterwards, or how deletes/edits would work — critical for an irreversible public-facing mutation.

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?

Two short sentences, zero redundancy, with the core action and its size constraint front-loaded before the validation tip.

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 publish mutation this is only adequate: it covers the size rule and the dry-run escape hatch, but omits authentication requirements, the fact that tags must come from a curated whitelist reachable via foto_suggest_tags/foto_search_tags, and any note on what happens on partial failure. All parameters are documented in the schema, so nothing is fully unexplained.

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 100%, so filePaths ordering, the 2-5 bound, tag whitelist, and dryRun semantics are already documented in the schema. The description only restates the photo count and dryRun behavior, adding no new meaning beyond the structured fields.

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 gives a specific verb and resource ('Publish a multi-image Series ... to Foto') and adds the 2-to-5-photo constraint, which implicitly separates it from foto_publish_post. It stops short of naming the single-post sibling explicitly, so an agent must infer the boundary.

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 second sentence is a genuine usage hint for the dryRun path ('validate locally without uploading'), but there is no guidance on when a Series is the right choice versus foto_publish_post or foto_draft_post, and no stated prerequisites such as requiring login for a real publish.

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