Focus Block Planner

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

Contradiction: annotations set readOnlyHint=true indicating read-only, but description says it 'drops a calendar time-block' which is a write operation. This inconsistency severely misleads the agent.

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?

Very concise single sentence, but truncated with '...' suggests incomplete thought. It could be clearer even in brevity.

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?

Despite simple input, the description lacks detail about behavior (e.g., does it modify reminders? how many blocks? what calendar?). The contradiction further reduces completeness.

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?

No parameters exist, and the description adds minimal value beyond the schema. With 0 parameters and 100% schema coverage, baseline 4 applies.

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?

Description clearly states it processes today's open reminders and creates calendar time-blocks, distinguishing it from sibling tools like create_event or list_reminders. However, the truncated ending '...' slightly undermines completeness.

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 explicit guidance on when or why to use this tool versus alternatives like manually creating events or completing reminders. The description only states what it does without context.

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