Upload text post

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

Annotations already indicate a write operation (readOnlyHint false), and description confirms publishing action. Adds detail about linkUrl behavior but no significant disclosure of side effects or required permissions. With annotations, description is adequate but not exceptional.

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, front-loaded with action, no redundant information. Every sentence adds value.

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?

Covers core functionality and key parameters like linkUrl and title. Does not detail all platform options but output schema exists for return values. For a tool with 10 parameters and nested objects, it provides sufficient context for an agent.

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?

Description adds platform-specific context for title and linkUrl beyond schema descriptions. Explains the platformOptions object's flexibility and silent ignore of unsupported keys. With 70% schema coverage, description compensates well.

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?

Clearly states the tool publishes a text-only post, distinguishing it from sibling tools like upload_video and upload_photos. The mention of title requirement for Reddit and linkUrl support adds specificity.

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?

Implicitly guides usage by stating 'text-only post', which excludes other media types. Does not explicitly list when-not or alternatives, but the context of sibling tool names makes the purpose clear.

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