bookshelf_create_remotepathmapping

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

The description adds 'WRITE: this modifies your Bookshelf instance', which provides explicit context that the operation is a mutating write action. Annotations already indicate readOnlyHint=false, but the description reinforces the behavioral impact. It does not contradict annotations and offers a small amount of additional context, though it misses details like idempotency or specific effects on resources.

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 only two sentences, so it is technically short, but the first sentence 'Create remotepathmapping' is purely redundant and does not earn its place. The second sentence adds a useful write warning, but overall the description is under-specified rather than efficiently 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?

This create tool has a generic body parameter, no parameter docs, and an output schema that is not referenced. The description does not explain the resource concept, required fields, or any constraints, despite the CRUD sibling set suggesting a typical create operation. It is minimally complete only in that it indicates a write operation, but it is inadequate for an agent to correctly invoke the tool.

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 defines a single 'body' object with additionalProperties true and no property descriptions, and the description provides zero information about what this body should contain. With 0% schema coverage and no parameter hints, an agent has no way to construct a valid remotepathmapping object, making the tool nearly unusable without external knowledge.

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 'Create remotepathmapping' directly restates the tool name, making it a tautology. It does not explain what a remotepathmapping is or what creating it entails, and while it distinguishes from siblings via the verb 'create', it adds no additional clarity beyond the name itself.

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 related tools like list_remotepathmapping, update_remotepathmapping, or delete_remotepathmapping. There is no mention of prerequisites, typical use cases, or alternatives, leaving the agent to infer usage from the tool name alone.

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