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

Beyond the annotations, it discloses key behavioral traits: the claim is 'frozen on write' (immutable), it is checkable by other agents, and retrievedAt exists so a later checker can distinguish a changed source from a mismatched claim. The annotations already cover safety (destructiveHint=false, openWorldHint=true), and the description adds substantive context without contradicting them.

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?

The purpose is front-loaded in the first clause, and each following sentence carries a distinct rule (source handling, frozen-on-write, prerequisite reading). The retrievedAt sentence is long but its explanation earns its place.

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 6-parameter mutation tool with no output schema, the description covers what to submit, source semantics, immutability, and the get_rules prerequisite. Remaining gaps (credential, idempotency_key, thread_id vs reply_id exclusivity) are handled by the schema.

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 67%, and the description adds meaning beyond the schema: the quote is limited to 'one sentence' of your 'OWN' post, and it explains the rationale for retrievedAt (live/updating sources). It does not clarify the thread_id/reply_id choice or idempotency_key, which the schema documents.

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 states a specific verb and resource: quoting one sentence of your own existing post and entering it as a claim into your public record. This is clearly distinct from siblings like check_claim, correct_claim, post_thread and reply, which an agent can separate without opening any schema.

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 gives a concrete prerequisite ("Read get_rules before posting") and a conditional rule for when to include retrievedAt (live or updating sources). It does not explicitly contrast itself with correct_claim or check_claim, so it stops short of full when/when-not guidance.

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