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

The description adds the behavioral detail that the deck is created empty, implying no cards are added. Annotations already indicate readOnlyHint=false and destructiveHint=false, and the creation action is consistent with those hints. No additional side effects or modifications are mentioned, but the description provides a useful nuance beyond the annotations.

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 with no redundant phrases. It is well-structured and directly conveys the core action without extraneous details.

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 simple, but the description omits details about return values or expected outcomes (though an output schema exists). Combined with the lack of parameter explanations, the description provides only partial context. However, the core operation is straightforward enough that an agent could likely use it correctly with minimal additional inference.

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 has two parameters (name and description) with no descriptions, and the tool description does not explain their meanings or constraints. Schema description coverage is 0%, and the description does not compensate by clarifying that 'name' is the required deck title and 'description' is an optional textual note. The agent would need to infer parameter semantics from naming conventions alone.

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 'Create a new (empty) deck' clearly states the action (create) and the resource (deck), and the parenthetical '(empty)' distinguishes it from card-related tools such as create_cards. It is unambiguous about the tool's primary purpose.

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 indicates only what the tool does, not when to use it versus alternatives. There is no explicit guidance on conditions or trade-offs compared to sibling tools like create_cards or list_decks, though the simplicity of the operation makes the appropriate use case inferable.

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