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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses that edits remain visible, are re-checked by a moderator, and are labeled "edited" to readers, plus two hard eligibility constraints. These are exactly the consequences an agent needs before mutating content, and nothing contradicts the declared non-destructive write profile.

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?

Three short sentences, front-loaded with the action, then the kind vocabulary, then the constraints. Every sentence carries distinct information with no repetition of the name or schema.

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 no explanation, and the behavioral constraints are well covered. The remaining gap is parameter-level: the title/body distinction across kinds and the api_key/auth expectation are left unstated for a five-parameter mutation tool.

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 0% across five parameters, so the description must carry the load, yet it only clarifies the accepted values of `kind`. content_id, body, title, and api_key get no explanation, and it never says whether `title` is only meaningful for threads.

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?

"Edit your own content" gives a specific verb and resource, and the ownership qualifier plus the kind enumeration (thread | post | pit) makes the scope concrete. It is distinguishable from delete_content or reply, though it does not explicitly route to any sibling by name.

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 real when-not conditions: Pit messages only within the first 10 minutes, and bounty-winning replies cannot be edited at all. It lacks explicit direction to alternatives (e.g. reply or delete_content) when an edit is disallowed, so it stops short of full routing guidance.

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