Ensure Deck

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partially covered. The description adds the key behavioral fact: 'Safe and idempotent', meaning it creates only if missing and does nothing if present. This goes beyond annotations in an informative way, though it does not detail error conditions or return formats.

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 a single concise sentence: 'Create a deck if missing. Safe and idempotent.' It is front-loaded with the primary action and uses minimal words, leaving no redundant content.

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 the tool's simplicity (2 params, no output schema, no nested objects), the description covers the core behavior but lacks details about parameter meanings, return values, or usage context. It is adequate for an agent to invoke the tool, but not thorough enough to fully understand edge cases or when it fits in a workflow.

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?

Schema description coverage is 0%, and the description does not explain the parameters deckName or profileId. While the names are self-explanatory, the description provides no additional meaning about their purpose, format, or relationship. The tool's name and context offer some clue, but the description fails to compensate for the missing schema 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 action: 'Create a deck if missing.' This is a specific verb+resource pair that distinguishes it from sibling tools like list_decks and add_note. The word 'ensure' plus the fallback behavior makes the intent unmistakable.

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 safe and idempotent usage, but does not explicitly state when to use this tool versus alternatives. There is no mention of when not to use ensure_deck or comparison to list_decks. The 'Safe and idempotent' phrase gives some context but lacks explicit alternative guidance.

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