aamio_board_withdraw

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds useful behavioral context beyond those: the post must be your own, it must be removed before expiry, and the removal affects all readers ('disappears for everyone reading the board'). 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?

Two short sentences with no filler. The core action and scope are front-loaded, and the second sentence adds a valuable behavioral consequence.

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 low-complexity, one-parameter destructive action, the description covers purpose, ownership, timing, and effect. The main missing piece is how to identify the post via the `post` parameter; there is also no mention of return behavior, though no output schema exists.

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 required `post` string. The agent can infer it refers to a board post, but not whether it should be a post ID, slug, or content, which is a meaningful gap for invocation.

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 ('Take... off the board') and resource (posts), and adds scope ('your own posts') and timing ('before it expires'). This distinguishes it from siblings like aamio_board_post (create), aamio_board_find (read), and aamio_board_answer (answer).

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?

It clearly conveys when to use the tool: for one of your own posts, before it expires. This gives solid contextual guidance, though it does not explicitly name alternatives or state when not to use it, stopping short of a 5.

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