repost_show

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is reversible via undo=True and implies a write/mutation, but omits permissions/auth requirements, whether reposting is idempotent, and what happens to an existing repost. That is partial disclosure for an unannotated mutation tool.

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 tight sentence with zero filler, and the core action is front-loaded before the optional modifier clause. Nothing could be trimmed without losing meaning.

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 simple two-parameter tool with no output schema and no annotations, the description covers the mutation and its reversal but leaves the required key argument and auth expectations unexplained. It is minimally viable rather than complete.

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 does explain the optional undo parameter's semantics ('undo=True removes the repost'), but the required 'key' parameter is left completely undefined — an agent cannot tell whether it is a show key, user key, or token.

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 (repost) and resource (show), so the action is unambiguous. It does not, however, differentiate from near-neighbor siblings such as favorite_show or listen_later, which an agent could easily confuse with reposting.

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?

There is no explicit when-to-use guidance and no named alternative among the siblings (favorite_show, listen_later, upload_show). The undo=True note hints at reversible usage but says nothing about when an agent should prefer this over other show-mutation tools.

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