post_bulletin_note

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

With no annotations, the description carries the full behavioral burden and delivers almost none of it. It implies a write operation but says nothing about required permissions, whether posting notifies store members, whether it is rate-limited, or what happens on success. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

A single front-loaded sentence with no filler; the core action and target are immediately clear. It is not padded, though the loose use of "Pin" costs a bit of precision.

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?

Adequate for selection purposes.

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 100%, so every parameter (title, message, store_id, is_pinned, note_color) is already documented in the schema; baseline 3 applies. The description adds no syntax, format, or constraint detail beyond the schema, and its use of "Pin" does not clarify the is_pinned parameter.

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?

States a concrete verb+resource: pinning/posting a note to the store bulletin board, with useful examples of content type (note, announcement, restocking alert). It is clearly distinguishable from get_bulletin_board and delete_bulletin_note, though it doesn't name those siblings. The verb "Pin" is slightly at odds with is_pinned defaulting to false, which introduces minor ambiguity about whether pinning is mandatory.

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 no when-to-use guidance: no prerequisites (store membership, permissions), no mention of when to prefer this over delete_bulletin_note or get_bulletin_board, and no exclusions. Usage is only implied by the tool's stated purpose. Content-type examples hint at scenarios but do not constitute routing guidance.

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