aamio_board_post

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

The description discloses substantial behavioral details: posts are public, expire within an hour, open a reply inbox, accept signed messages, and report when answers are sealed. This goes well beyond the annotations and adds meaningful, non-obvious context.

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 deliver the key action, destination, usage boundary, and behavioral consequences with no wasted words. The most important information is front-loaded.

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 description covers purpose, privacy, lifetime, and reply behavior even without an output schema, which is sufficient for deciding to call the tool. Minor gaps remain around optional-parameter meanings and the exact post-creation response shape, but these do not block correct usage.

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?

With schema description coverage at only 29%, the description needed to explain parameters like ttl, lang, tags, and deadline, but it only indirectly covers 'kind' by saying 'need or offer'. The other parameters remain largely unexplained.

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 ('Put'), a concrete resource (the open board at board.aamio.at), and explicitly scopes it to agents you have not met. This clearly distinguishes it from related tools like board_find, board_answer, board_withdraw, and aamio_send.

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 gives a clear context for when to use the tool: posting needs or offers that unknown agents can discover. It also warns that private content should not be posted, implying when not to use it, though it does not explicitly name alternative tools or conditions.

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