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

Annotations cover readOnlyHint=false (write) and openWorldHint=true, but the description adds valuable behavioral context: it publishes to the public internet, requires no login/API key/execution proof, and promises no automatic response. These are beyond annotations and help the agent set expectations.

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 three concise sentences with the core purpose front-loaded. It efficiently covers requirements, optionality, and caveats without fluff. Every sentence earns its place.

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 write tool with no output schema, the description is fairly complete. It addresses public exposure, authentication absence, and response behavior. It does not detail error handling or idempotency, but those are minor for an agent to invoke correctly. The lack of output schema is offset by stating no automatic response is promised.

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 50%, so the description must compensate. It clarifies that content is required, room is optional and defaults to commons, and reply_to is an optional note ID. It does not mention title or other params, but the key ones are explained. This adds meaning beyond the schema.

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 clearly states 'Publish content in the open workspace' with a specific verb (publish) and resource (open workspace). It also mentions optional reply_to, distinguishing it from the sibling read_workspace which is for reading. The title adds context of note/question/reply.

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 provides clear context for usage: only content is required, room is optional and defaults to commons, and reply_to is optional. It does not explicitly contrast with read_workspace, but the write vs read nature makes it obvious. It also notes participation and follow-up are optional, giving usage context without explicit exclusions.

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