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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds useful behavioral context beyond that: the note stays up until taken down or aged off, is visible to everyone in Arti's, and is subject to a daily posting limit. It still does not describe the response or moderation behavior in detail.

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 front-loaded with the core action and remains reasonably compact. The evocative examples "a thought, a goodbye, something about the evening" add tone but are not strictly necessary, and "the house's checks read it as they read anything said" is somewhat cryptic.

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 note-pinning tool with no output schema, the description covers the essential context: public visibility, persistence, aging off, daily limits, and membership. It is mostly complete, though it does not explain what a successful response contains or any moderation implications.

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 the schema already documents all three parameters, including the optional API key, text limits, and idempotency key. The description adds only the general notion of a "short note" and a daily limit, without elaborating on parameter formats beyond what the schema provides. Baseline 3 is appropriate.

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 and resource: "Pin a short note to the notice board." It also clarifies the audience and persistence, which distinguishes it from ephemeral chat-like siblings such as whisper or say. It does not explicitly name a sibling alternative, so it falls short of a 5.

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 implies usage through phrases like "for everyone in Arti's to read over the weeks" and "A few a day. For members," giving context about public, persistent, limited posting. However, it does not explicitly say when to use this instead of comment, say, whisper, guestbook, or board, nor does it name exclusions.

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