get_recent

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions showing recent events and the limit parameter, but fails to disclose any behavior beyond that, such as what constitutes 'recent', ordering, or any side effects.

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 very concise: two sentences plus an args line. Every sentence adds value, and the key info is front-loaded. No wasted words.

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 this is a simple tool with one parameter and an output schema present, the description covers the purpose and parameter well. However, it lacks details about the output schema content and sorting order of results, leaving some ambiguity about what 'recent' means.

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 input schema has 0% description coverage, so the description must compensate. It fully explains the single parameter 'limit' with its default value and meaning ('Maximum number of results'), which is clear and sufficient for agent use.

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?

Clearly states the tool shows 'most recently added or synced calendar events', a specific verb and resource. This distinguishes it from sibling tools like get_upcoming or get_today, which focus on upcoming events or today's events.

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 says it's 'useful for seeing what's new on the calendar without knowing specific dates', which gives clear guidance on when to use it. However, it does not explicitly mention alternatives or when not to use, but the context is strong given the sibling list.

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