calendar_list_get

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

With no annotations, the description carries the full burden of disclosure. It indicates a read operation ('Get') but does not specify that it is read-only, require permissions, or describe any side effects or limitations. The behavior is under-documented.

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 concise sentence, which is appropriate for a simple tool. However, it lacks essential details like the return value, making it under-informative. It is short but not fully effective.

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 parameter, no output schema, and no annotations, the description should explain what the tool returns (e.g., calendar entry metadata). It does not, leaving the agent without essential context about the response. The tool's role among siblings is also unclear.

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 single parameter 'calendarId' is fully documented in the schema with a clear description. The description adds only the phrase 'specific calendar entry', which does not enhance understanding beyond the schema. Schema coverage is 100%, so the baseline score of 3 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 states the verb 'Get' and resource 'specific calendar entry', which clearly identifies the action. However, it does not differentiate from sibling tool 'calendar_get_calendar', which also retrieves a calendar. The term 'calendar entry' is somewhat ambiguous without context.

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 like 'calendar_get_calendar' or 'calendar_list_calendars'. There is no mention of prerequisites, conditions, or exclusions, leaving the agent to infer usage from the name alone.

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