calendar-get_or_create

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

With no annotations, the description should disclose behavioral traits. It mentions 'gets or creates' implying idempotency, but does not clarify what happens if the calendar already exists (return vs update), any side effects, authentication needs, or error conditions. The description is too minimal for safe invocation.

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 sentence, which is concise. However, it is too short to provide adequate context. There is no wasted text, but the brevity impacts completeness.

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 tool has one optional parameter and no output schema, the description still falls short. It does not explain what the tool returns, how it handles existing vs. new calendars, or any constraints. Contextual completeness is low.

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 optional parameter 'name' with a description. The tool's description adds no extra meaning; in fact, it says 'the main calendar' which conflicts with the schema allowing a custom name. This could mislead the agent into thinking the tool only works with a fixed calendar.

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 clearly states the tool gets or creates a calendar resource, with a specific verb and resource. However, it refers to 'the main calendar' without defining what 'main' means, and there is a sibling tool 'calendar-get_or_create_day' but the distinction is clear as this one deals with the calendar itself, not days. It could be more specific about which calendar is considered main.

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 provides no guidance on when to use this tool versus alternatives or when not to use it. It only states the basic action without context on prerequisites, fallback behaviors, or related tools.

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