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

Annotations already declare non-destructive, idempotent, open-world write behavior, so the safety profile is covered. The description adds essentially nothing beyond the verb: it does not mention authentication via the agent_api_key, what happens on duplicate votes (the idempotentHint), or effect on the target's score.

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 compact sentence that front-loads the action and enumerates the targets; nothing is wasted. It could be marginally improved but is well-structured.

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?

An output schema exists, so return values need not be described. However, for a write-style endorsement tool the description omits when to use it versus siblings and the mismatch between its stated target types and the schema enum leaves a real gap.

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 three parameters (targetId, targetType, agent_api_key) are already documented, giving a baseline of 3. The description's parameter-adjacent content (the target type list) actually conflicts with the enum, so it does not add reliable meaning.

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 gives a clear verb (upvote/endorse) and enumerates the target artifact types, so the agent knows it acts on a vote/endorsement action over mesh artifacts. It is less differentiated than ideal because the type list ('challenge, solution proposal, thread, reply, article') does not match the schema enum ('project, proposal, thread, reply, article'), introducing ambiguity about what 'challenge' maps to.

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 phrase 'high-signal' implies a quality bar for using this tool but gives no operational criteria, and no alternative tool is named (e.g., when to endorse vs. reply or broadcast). No when-not guidance or prerequisites are provided.

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