update_publication_titles

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

No annotations, so description carries the burden. It explains merge semantics, partial update, and no-op behavior. Lacks details on permissions or side effects, but the behavioral traits are well-articulated for a mutation tool.

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?

Exceptionally concise: two sentences, front-loaded with 'partial update', no unnecessary 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 an output schema exists, return values need not be explained. The description covers merge semantics, optionality, and no-op case. It is complete enough for a 4-param mutation tool, though missing permission notes.

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 0%, so description must compensate. It explains that 'headers' and 'descriptions' are per-language maps with merge behavior and that omitted languages are preserved, adding significant meaning beyond the schema's type-only info.

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 it performs a 'partial update' on 'publication title and/or per-language headers and descriptions', using a specific verb and resource. It distinguishes from siblings like 'update_publication_flags' by focusing solely on title-related fields.

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?

Provides clear guidance on how to use: merge behavior for headers/descriptions (only pass languages to change) and no-op if all optional args omitted. Lacks explicit when-not-to-use or alternatives, but context is sufficient for typical use.

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