Upload text post

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

Annotations indicate readOnlyHint=false (write), openWorldHint=true, destructiveHint=false. The description adds behavioral context: publishing a post, title requirement for Reddit, and link preview attachment. It does not contradict annotations and provides useful extra information beyond the structured fields.

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 sentences, no filler. The first sentence immediately states the primary action, and the second adds critical nuance about linkUrl and Reddit. Every word 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?

Despite having 14 parameters and a complex nested options object, the description only covers the core purpose and linkUrl. It does not mention scheduling, autogeneration, queue, or platform-specific overrides. The output schema exists but the description could give more high-level guidance on parameter interaction.

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 79%, so the description adds value by clarifying that 'Title is required for Reddit' (not just generally required) and that linkUrl attaches a link preview. These details are not obvious from the schema alone.

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 clearly states 'Publish a text-only post' with a specific verb and resource. It distinguishes from sibling tools like upload_photos and upload_video by specifying 'text-only', and adds detail about link preview support.

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 implies usage for text-only posts and mentions that title is required for Reddit, but does not explicitly state when to use this tool vs alternatives like upload_document or when not to use it. No exclusions or alternatives are named.

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