bookshelf_update_metadata

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior (destructiveHint=false). The description explicitly states 'WRITE: this modifies your Bookshelf instance,' which reinforces the annotation but adds limited new behavioral context. It mentions the forceSave query param but does not explain its effect.

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 and front-loads the purpose. The middle sentence about query parameters is awkward and adds little value, but the overall length is appropriate with no fluff.

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 it is a write operation with a nested body parameter and many sibling tools, the description is too sparse. It does not explain what metadata is being updated, the structure of the body, the effect of force_save, or when this action is necessary. The existence of an output schema helps with return values but not with usage context.

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 0%, so the description must compensate. It mentions 'forceSave' but with a name mismatch (schema uses force_save) and provides no explanation of what it does. The required 'id' and 'body' parameters are completely undocumented in the description.

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 'Update metadata' which is a specific verb+resource, and it distinguishes itself from sibling create/get/delete metadata tools. However, the object 'metadata' is somewhat generic and could be ambiguous without knowing the context of the Bookshelf instance.

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 no guidance on when to use this tool versus alternatives like create_metadata, delete_metadata, or update_author. It implies usage for updating metadata but lacks any context about prerequisites, exclusions, or preferred scenarios.

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