bookshelf_list_calendar

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

The readOnlyHint annotation already indicates a read operation. The description adds no behavioral context beyond that, such as what data is returned, date range semantics, or default behavior when parameters are omitted. No contradiction with annotations.

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 brief, but brevity is not conciseness here—it omits critical context. The list of param names is not structured or explained, and the sentence 'List calendar' is an under-specification rather than a concise statement.

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?

With an output schema present, return values are covered, but the tool's purpose remains underspecified. It fails to clarify whether this lists events, releases, or something else, and doesn't address the existence of a sibling get_calendar tool. Complexity is low, yet the description still feels incomplete.

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 explain parameters. It only lists names (start, end, unmonitored, includeAuthor) without defining formats, defaults, or meaning. Also, it uses 'includeAuthor' while the schema uses 'include_author', adding confusion.

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 'List calendar' names a verb and resource but is vague. It doesn't specify what kind of calendar or what the list contains, and it fails to differentiate from the sibling tool 'bookshelf_get_calendar'.

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 on when to use this tool vs alternatives. The description merely lists query parameters without explaining the use case or exclusions. It doesn't mention that 'get_calendar' exists for retrieving a single calendar item.

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