bookshelf_test_indexer

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

The description states 'WRITE: this modifies your Bookshelf instance,' which adds some behavioral context beyond the annotations (readOnlyHint=false, destructiveHint=false). However, it does not disclose specific side effects or what exactly gets modified.

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 short and front-loaded, but it consists of disjointed fragments ('Create indexer test.', 'Query params: forceTest.', 'WRITE...') that lack a coherent structure. It is concise but under-specified.

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?

The tool has a body parameter and no required parameters, making it unclear how to target a specific indexer for testing. The description does not explain the expected body content or how to specify the indexer, leaving the input side incomplete despite the presence of an output schema.

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%, and the description does not compensate. It mentions 'forceTest' but does not explain its meaning or the 'body' parameter, which is an untyped object with additionalProperties true. The agent is left without any hint of what payload to send.

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 indexer test' is vague and does not specify what the test does or how it differs from sibling tools like bookshelf_test_all_indexer. It adds a WRITE note, but the core action is ambiguous.

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, or what inputs are needed to target a specific indexer. The description does not mention exclusions, prerequisites, or context.

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