bookshelf_test_notification

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

The description explicitly says 'WRITE: this modifies your Bookshelf instance,' which is useful because the tool name might suggest a read-only test. This aligns with the annotations (readOnlyHint=false, destructiveHint=false) and adds context about instance modification, but it does not disclose other potential side effects (e.g., whether a real notification is sent).

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 concise, consisting of three short fragments that are immediately scannable. No unnecessary words or repetition of schema information.

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 tool that tests notifications, the description doesn't explain what a 'notification test' entails, how to specify which notification to test, or how it differs from testing all notifications. The output schema covers return values, but the operational context is severely under-described, especially for a mutation 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?

Schema coverage is 0%, so the description must compensate for parameters. It mentions 'Query params: forceTest' but does not explain what forceTest does or the role of the 'body' parameter. The camelCase mention ('forceTest') also differs from the schema's snake_case ('force_test'), which could confuse the agent.

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 action ('Create notification test') with a clear verb and resource, indicating the tool creates a test for notifications. However, it does not explicitly distinguish this from the sibling 'bookshelf_test_all_notification' or clarify the exact nature of the test, so it falls short of a perfect 5.

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 lacks any guidance on when to use this tool versus alternatives like 'bookshelf_test_all_notification' or 'bookshelf_action_notification'. It only mentions query parameters and a write warning, but no context for selecting this tool in the workflow.

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