bookshelf_create_metadata

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

Annotations already indicate readOnlyHint=false, and the description adds 'WRITE: this modifies your Bookshelf instance,' which reinforces the mutating nature. However, it does not disclose side effects beyond modification, such as whether forceSave overwrites existing data or requires specific permissions. 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 very brief and front-loaded with the purpose, then a parameter note and a behavior warning. Each sentence serves a distinct function with no fluff, though it is arguably too sparse.

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?

Even with an output schema present, the input side is under-specified. The body parameter is a free-form object with no hints about required fields or examples, and the description does not explain what 'metadata' means in this domain or how to construct a valid request. This is inadequate for a create operation.

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 the description must explain parameters. It only identifies forceSave as a query parameter, which is already in the schema as a boolean property, but does not explain its purpose or the structure/meaning of the body parameter. This is insufficient for a body with arbitrary additional properties.

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 states a clear action ('Create') and resource ('metadata'), but 'metadata' is vague and does not distinguish this from related tools like create_metadataprofile or the broader create_* family. It lacks scope or context to clarify what metadata entity is being created.

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 such as update_metadata or get_metadata. It mentions a query parameter but no usage context or preconditions.

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