bookshelf_create_metadataprofile

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

The description explicitly states 'WRITE: this modifies your Bookshelf instance,' which adds a clear behavioral warning. The annotations already indicate readOnlyHint=false, but the description reinforces the write nature and potential impact, providing useful context beyond the structured fields.

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 exceptionally concise, containing two short sentences that state the action and the write warning. Every word earns its place with no redundancy or filler.

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 create operation with a generic 'body' parameter, the description is incomplete. It does not explain what a metadataprofile is, what fields the body should include, or any prerequisites. The presence of an output schema does not compensate for the lack of input guidance.

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?

The tool has one parameter 'body' with no schema description (0% coverage) and the description does not mention parameters at all. The agent receives no guidance on what the body should contain or how to structure the create request, making this parameter entirely opaque.

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 'Create metadataprofile' with a specific verb and resource. It is unambiguous about the action being performed. However, it does not differentiate from sibling tools like update or get beyond the verb, though the name itself provides that distinction.

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 guidance is provided on when to use this tool versus alternatives such as update_metadataprofile or get_metadataprofile. The description lacks context for selecting this create operation over other profile-related tools.

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