get_calendar

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals the default window and that results include release date types and on-disk status, but it does not disclose pagination, sorting, output structure, or whether the operation is purely read-only beyond the verb 'List.'

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 a single efficient sentence with no filler. The core action is front-loaded, followed by the key scoping details and the default behavior.

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 read-only listing tool with fully documented optional parameters, the description covers the essential call context: what is listed, the date-window concept, release-date subtypes, on-disk status, and default range. Minor gaps remain around pagination and exact output formatting, but the lack of an output schema is partially compensated by the description's mention of fields returned.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the 'window' concept and the default of the next 30 days. It does not add much for tags or unmonitored, but those are already clearly described in the 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 a specific verb and resource: 'List movies with a release date in a window.' It further differentiates itself by specifying cinema, digital, and physical release dates plus on-disk status, which clearly separates it from sibling tools like list_movies.

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 clearly implies usage for date-windowed movie release queries, especially with the default 'next 30 days' behavior. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough for an agent to select it appropriately.

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