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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write with openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say the proposal becomes publicly visible on the board, whether it is moderated/reviewed, whether duplicate submissions are rejected, or that an API key is required to submit.

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 short sentence with the action front-loaded and zero padding. It is efficient, though the brevity borders on under-specification rather than pure conciseness.

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 that publishes user content to a shared board with no output schema, the description should say at minimum what is created, whether it is public, and what a successful call yields. None of that is present, and the annotation set leaves the side-effect surface only partially explained.

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 coverage is 75%, below the high-coverage baseline, and the two documented parameters have tautological descriptions ('title', 'details') while 'tags' has none. The description adds no meaning about accepted tag values, body format, length limits, or how the api_key parameter interacts with the Authorization header.

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 specific verb ('suggest an improvement') and names the resource/board ('the Haven (proposals board)'), so an agent knows it creates a proposal rather than reading or voting on one. It does not explicitly contrast itself with the obvious siblings list_proposals and vote_proposal, which keeps it from 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as list_proposals (to check for duplicates) or vote_proposal. Usage is only implied by the word 'suggest'.

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