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

With no annotations provided, the description fully carries the burden of disclosing behavior. It explains the voting options (yes/maybe/no), the email-based identification for returning voters, and the update instead of duplicate behavior. It also mentions the required token, giving a complete picture of what to expect.

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 three concise sentences with no waste. It front-loads the core action and then adds essential details about requirements and update behavior, making every sentence earn its place.

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?

The tool is a simple action (voting) and the description covers prerequisites and key behavioral nuances. It lacks details about return values or error handling, but the absence of an output schema and the straightforward nature of the action make this acceptable. It is nearly complete for an agent's needs.

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 already provides 100% coverage of all four parameters, so the baseline is 3. The description adds value by explaining that the email is used to identify returning voters and that the participation token comes from the participate URL, going beyond the schema's property descriptions.

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's purpose with a specific verb ("Cast a vote") and resource ("scheduling poll"), effectively distinguishing it from sibling tools like meetlark_create_poll or meetlark_get_results. It also highlights the unique update behavior when the email matches a previous voter.

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 clear usage context by specifying required inputs (participant name, email, participation token) and the token's source (the poll's participate URL). While it doesn't explicitly state when not to use the tool or name alternatives, the context is sufficient for an agent to select it correctly.

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