bookshelf_get_notification_schema

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

The annotation readOnlyHint=true already establishes that this is a safe read operation. The description adds no additional behavioral context beyond this annotation; it does not explain what the schema contains, how it should be interpreted, or any other side effects. There is no contradiction, but the description adds zero value beyond the annotation.

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 short, which is concise, but the phrase 'List notification schema' is not a well-structured sentence and sacrifices clarity for brevity. The use of 'List' with a singular noun is awkward, and the description would benefit from being a complete, meaningful sentence.

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?

Despite having an output schema, the description does not explain the broader purpose of the tool within its CRUD family. An agent would not understand that this tool returns the JSON schema defining valid fields for notification objects, which is critical for creating or updating notifications. The description relies entirely on naming conventions and sibling patterns.

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 tool has zero parameters, and the input schema fully documents this with an empty properties object. The description adds nothing about parameters, but none exist, so the baseline score of 4 is appropriate.

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 identifies a 'notification schema' resource and the action 'List', which distinguishes it from sibling tools like get_notification and list_notification. However, the phrase is vague and grammatically awkward ('schema' is singular), leaving ambiguity about whether it returns a list of schemas or the schema for notifications.

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. It does not mention that the schema is useful for understanding notification fields before create/update operations, nor does it provide any context for when this endpoint would be called.

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