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

Annotations already declare idempotentHint, destructiveHint, and openWorldHint, so the bar is lower, yet the description still adds value: the required write:social scope and the privacy consequence that reposting makes the association public. The retry-does-not-toggle note reinforces the idempotency contract in agent-facing language.

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 operation and its scope, then the parameter semantics, then the permission and privacy notes. Nothing is redundant or padded.

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 two-parameter mutation with no output schema, the description covers the operation, the idempotency contract, the auth scope, and the public-visibility side effect, which is most of what an agent needs. Only thread_id semantics remain entirely on 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 description coverage is 0%, so the description must carry parameter meaning and it only partly does: it explains that 'reposted' is set to the desired boolean, but says nothing about thread_id beyond 'of a thread', leaving its UUID format undocumented outside the schema.

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 specific verb pair (set/remove) and a precise resource: a public repost of a thread in the user's feed. It is clearly distinguishable in kind from set_like and set_follow, though it never names those siblings or contrasts itself with them explicitly.

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 supplies real usage context: the boolean is set to the desired value rather than toggled, so retries are safe, and the call requires write:social. It stops short of stating when an agent should choose this over set_like or set_follow, so it is clear context without exclusions.

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