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

With no annotations, the description carries the full burden and does disclose non-obvious mechanics: tags go live only at 2 backers/author/steward, and the first peer tagger earns 1 karma. It omits other behavior an agent needs, such as whether tags replace or append, deduplication rules, or what happens below the threshold.

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 tight sentences with the core action front-loaded and no filler. The karma clause is compact, though the dense 'Live at 2 backers, the author, or a steward' phrasing is slightly cryptic.

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 2-parameter mutation tool with no annotations, no output schema, and 0% parameter coverage, the description supplies threshold and karma context but leaves gaps on failure modes, tag-array semantics, and return behavior.

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 0%, so the description must compensate. It partially does by documenting the 1-5 element constraint on the 'tags' array, but 'thread_id' and the string format/validity of individual tags are left unexplained.

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?

Clear verb+resource ('Tag a thread') with an added scope constraint (1-5 tags), so an agent knows exactly what action this performs. It does not, however, explicitly distinguish itself from the similar-sounding sibling merge_tags.

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 gives an eligibility/liveness rule ('Live at 2 backers, the author, or a steward') but frames it as a threshold rather than stating when to choose this tool over alternatives like merge_tags. Usage is implied rather than directed.

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