select_emotion_card

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

Discloses auto-targeting behavior for SelectOne cards, adding value beyond schema. However, lacks details on error handling (e.g., invalid index) or side effects, and no annotations to supplement.

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?

Two sentences: first states purpose, second provides workflow and special behavior. No filler, every sentence adds value.

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?

Covers core workflow and key behavior. With output schema present, return value details are acceptable. Could mention edge cases like out-of-range index, but overall complete for its complexity.

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?

Only parameter is 'index'. Description adds crucial context: 0-based indexing and prerequisite step. Schema has no description (0% coverage), so description compensates well.

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 action (select) and the resource (emotion card by index). It distinguishes from sibling tool get_emotion_candidates by specifying that this tool is called after viewing options.

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?

Provides explicit workflow: call get_emotion_candidates first, then use this with chosen index. Also mentions handling of SelectOne cards. Missing explicit when-not-to-use but guidance is strong.

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