bookshelf_create_rootfolder

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

Annotations already indicate a write operation (readOnlyHint=false). The description repeats this with 'WRITE: this modifies your Bookshelf instance' but adds no new behavioral details such as side effects, reversibility, or required filesystem state. It is largely redundant.

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 short, but the second sentence ('WRITE...') merely restates the readOnlyHint annotation, so it wastes the only additional sentence. It is under-specified rather than concise.

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 creation tool with an unstructured body, the description is grossly incomplete. It fails to explain what a rootfolder is, what configuration the body should contain, or any prerequisites. The presence of an output schema does not compensate for the missing 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 schema has a single 'body' parameter with no description and additionalProperties: true, giving no structural hints. The description does not mention what fields to include (e.g., name, path), leaving the agent without any guidance for constructing the request.

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 the verb 'Create' and resource 'rootfolder', clearly identifying the action. It is distinct from sibling tools like update/delete/list rootfolder, though it does not explain what a rootfolder is.

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 about when to use this tool, prerequisites (e.g., folder must exist), or alternatives. The create verb implies use, but no context is given.

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