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

Annotations only indicate non-read-only and non-destructive behavior. The description adds meaningful behavioral context: boardLabel can find-or-create a board, and enrichment is best-effort and never blocks the save. This goes beyond the annotations, though it does not address error or conflict behavior when params are combined.

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?

Three sentences, each earning its place: the core save action, the important boardLabel behavior, and the enrichment caveat. The most relevant guidance is front-loaded, with no filler or repetition of schema 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?

For a tool with four optional params and no output schema, the description covers the main behavioral nuance and gives enough context to use it safely. It does not state the return/success shape or what happens if url/text or board context is missing, but these are minor gaps for a straightforward capture tool.

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 coverage is 100%, so the baseline is 3. The description adds extra semantics by telling the agent to use boardLabel without boardId in a conversational context and by clarifying that enrichment is non-blocking. This is useful guidance beyond the schema's per-parameter 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 opens with a specific verb and resource: 'Save a link or a note as an idea on a board.' The phrase 'generic capture inbox for idea boards' distinguishes this from board-management siblings like idea_board_create and idea_list. An agent can clearly tell this is the capture/write tool for ideas.

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 gives explicit in-tool usage guidance: 'Pass boardLabel with no boardId to find-or-create a board by that freeform label,' and explains why this matters in a conversational client. It does not explicitly mention when to choose idea_add over sibling tools, but the context is clear enough to avoid obvious confusion.

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