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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the safety profile is covered. The description adds real value beyond that: it discloses the token requirement, the return shape (argument id and URL), the blind-first-ballot voting flow, and the one-revision rule. Only rate limits or error behavior are absent.

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?

Front-loads the action and the routing rule before the mechanics, and the example payload is useful rather than padding. It is dense and slightly long, mixing voting context with invocation guidance, but every sentence carries information.

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?

With no output schema, the description compensates by stating the return values (argument id and URL) and the token flow. Token acquisition, the answering relationship, and the sibling exclusion are all covered. A note on failure modes when the proposal is closed or the token is missing would make it complete.

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 100%, so the baseline is 3. The description does clarify the intent of because_argument_id ('names the argument you are answering') and shows a concrete example payload, but this largely restates what the schema already documents for each field. No syntax or format detail 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?

States a specific verb and resource ('File a public argument for or against an open Folkmoot proposal') and immediately distinguishes itself from the sibling folkmoot_post ('Not for general discussion'). An agent can pick this over the other folkmoot_* tools without inspecting schemas.

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?

Gives an explicit trigger ('Use when you have a reason nobody has given yet'), names the exclusion ('Not for general discussion (folkmoot_post)'), and explains what because_argument_id is for. Alternatives and when-not conditions are both present.

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