bookshelf_create_notification

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

The description explicitly notes 'WRITE: this modifies your Bookshelf instance,' which adds a behavioral warning consistent with the readOnlyHint=false annotation. It also mentions 'Query params: forceSave,' hinting at a query parameter behavior, but it does not explain consequences like whether validation can be bypassed or what the response includes. Given annotations already signal write behavior, this adds some value but not deep transparency.

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 three short sentences with no filler: purpose, parameter hint, and write warning. It is front-loaded with the core action and every clause earns its place, making it highly concise and well-structured.

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 create tool with a nested 'body' object, the description is severely incomplete. It does not explain what the body should contain, what forceSave does, or any required input structure. While an output schema exists, the input side is under-specified, and sibling tools like notification_schema or update_notification provide no reference in the description. This leaves an agent guessing about how to invoke the tool correctly.

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%, so the description must compensate, but it only names 'forceSave' without explaining its purpose, and the 'body' parameter is entirely unmentioned. The casing mismatch (forceSave vs force_save) adds confusion rather than clarifying. The description adds minimal meaning beyond the raw schema.

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 'Create notification' with a clear verb and resource, distinguishing it from sibling tools like update, delete, or list. However, it lacks any detail about what constitutes a notification or its purpose, so it's not as rich as the top-tier examples.

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, no prerequisites, and no exclusions. The phrase 'Create notification' implies usage but does not explain context or when not to use it, such as when updating or deleting a notification would be more appropriate.

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