dooray_calendar_calendars

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

No annotations are provided, and the description only states 'find dooray calendars'. It does not disclose whether this is a read-only operation, what the response contains, or any side effects. The description carries the full burden and fails to deliver.

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, consisting of only three words. While concise, it is under-specified and lacks sufficient detail to be actionable. It is not appropriately sized because it omits critical 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?

Given the absence of an output schema and annotations, the description should explain return values and behavior, but it does not. Even for a simple tool, the description is incomplete and leaves the agent with unanswered questions.

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 schema has 100% coverage for the single 'operation' parameter, which includes an enum value 'find_calendars'. The description adds no additional meaning; it simply restates the operation. The schema's own parameter description is generic, so the tool description does not enhance understanding.

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 uses the verb 'find' and the resource 'dooray calendars', clearly indicating a retrieval operation. However, it does not specify whether it lists all calendars or searches by criteria, and it doesn't explicitly distinguish from sibling calendar tools, though the sibling tool names suggest different actions.

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?

There is no mention of when to use this tool versus alternative calendar tools like dooray_calendar_events or dooray_calendar_post_event. The description provides no context for selecting this tool.

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