calmesh_decide_poll

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

With no annotations provided, the description carries the full burden. It discloses the state change ('Marks the poll as decided') and the required scope, but does not mention reversibility, idempotency, or behavior if the poll is already decided. This is adequate but not deeply transparent.

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 two concise sentences that lead with the purpose, then add essential requirement information. There is no filler or redundancy.

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?

For a simple 2-parameter mutation tool with no output schema, the description covers purpose, state change, and scope requirement. It omits details about success/error behavior and edge cases like already-decided polls, but the operation is simple enough that the description is mostly sufficient.

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 describes both parameters (slug and decided_time) with full coverage, so the baseline is 3. The description adds no additional parameter-level guidance beyond what the schema already provides.

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 specific action 'Finalize a poll by selecting the decided meeting time' and identifies the resource (poll) and the state change (Marks the poll as decided). This distinguishes it from sibling poll tools like calmesh_create_poll and calmesh_list_polls.

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 implies when to use this tool (when a poll needs to be finalized) and provides a prerequisite ('Requires "book" scope'), but it does not explicitly name alternatives or exclusion conditions. The context is clear enough for a distinct action.

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