bookshelf_test_metadata

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

The description explicitly states 'WRITE: this modifies your Bookshelf instance', which aligns with readOnlyHint=false and adds context that it is a mutating operation. However, it does not specify what modifications occur or any side effects beyond that, leaving gaps.

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 but under-specified, consisting of loose fragments. It is not truly concise because each part provides minimal valuable information, leaving important details unaddressed.

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 write operation with an object parameter, the description is inadequate. It does not explain what constitutes a 'metadata test', what the 'body' should contain, or what 'force_test' does, making it incomplete despite having 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?

The description mentions 'Query params: forceTest' but the schema uses 'force_test', creating a naming mismatch and confusion. It does not explain the 'body' object parameter at all, and with 0% schema coverage, the description fails to add any meaningful parameter semantics.

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 phrase 'Create metadata test' is vague and could imply creating a test entity rather than triggering a validation. It also does not distinguish this from the sibling tool 'bookshelf_test_all_metadata', lacking a clear resource scope.

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 versus alternatives like bookshelf_test_all_metadata. The description only mentions a query parameter and a write warning, with no context for selection.

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