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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so safety is partly covered. Beyond that the description discloses two useful behaviors: duplicate/matching submissions are handled as upvotes rather than new records, and confirmation is mandatory before the write. It does not explain the confirm=dry-run flag or what a duplicate does to the caller.

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?

Two sentences, no filler, and the core purpose is front-loaded ahead of the imperative guardrail. Every sentence carries distinct information; nothing could be cut without losing meaning.

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 simple mutation tool with no output schema and annotations that cover the write/idempotency profile, this is close to sufficient: the agent knows what it does, the confirmation requirement, and the dedup path. Minor gaps remain around exactly how 'matching' is determined and how farmId scopes requests.

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 farmId, title, description, area, confirm, and idempotencyKey. The description adds no parameter-level detail (e.g., that 'confirm' implements the confirmation requirement) and only implicitly gestures at the confirm flag. Baseline 3 applies.

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 uses specific verbs and a specific resource: 'Submit a new feature request or upvote an existing matching request.' An agent immediately knows this is a write into the feature-request backlog. It does not name the read counterpart (get_feature_requests) or otherwise differentiate itself from siblings, 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?

It defines the two entry conditions ('new request' vs 'existing matching request'), which is real routing logic, and adds an operational rule ('ALWAYS ask for confirmation before writing'). It never names an alternative tool or an explicit when-not-to-use case, so it stops short of 5.

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