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

Annotations already signal readOnlyHint=false and destructiveHint=false, and the description confirms a creation side effect. It adds useful semantic context about idea boards being non-committal and pre-trip, but does not disclose return behavior, prerequisites, or other side effects; no contradiction with 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 compact sentence that front-loads the action and adds a purposeful parenthetical. Every word contributes either to the action or to the conceptual context, with 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 two-parameter create operation with fully documented schema and safety annotations, the description is nearly complete. It clearly communicates the tool's purpose and semantics; the only notable gap is that it does not describe what the call returns, though this is not essential for correct invocation.

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 provides full descriptions for both parameters (label and description), so the description does not need to repeat them. It adds no parameter-level guidance, matching the baseline for high schema coverage.

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 states a specific verb-resource pair ('Create a new idea board') and adds a clarifying parenthetical defining it as a non-committal, pre-trip destination scratchpad. This clearly distinguishes it from other idea_board_* tools and trip-focused tools.

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 parenthetical implies the intended use case (pre-trip, non-committal scratchpad) but does not explicitly state when to use this tool versus alternatives like trip_create or idea_add. There is no when-not-to-use guidance or routing to sibling tools.

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