Create or schedule a post

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

Annotations only convey write intent, open-world semantics, and non-destructiveness. The description adds substantial behavioral context: posts go out publicly under the user's brand, confirmation is required, text is validated before sending, and problematic posts are saved as 'withErrors'. No contradiction with annotations.

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 description is compact and front-loaded with the core purpose, then moves through state semantics, media prerequisite, validation, and user confirmation. Every sentence carries distinct, necessary information without redundancy.

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 9-parameter writing tool with an output schema, the description covers scheduling, drafts, media handling, validation, and social accountability. Nothing essential is missing for an agent to understand when and how to invoke it correctly.

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 89%, so the baseline is 3. The description adds relational meaning beyond the schema by linking 'ready' with a future publish_date for scheduling and by framing files as ids that must come from upload_media. It does not further explain publication_type or title, but the schema already covers those.

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 opens with 'Publish now or schedule a post on ONE connected account,' naming the specific verb, resource, and scope. This clearly distinguishes it from listing, getting, updating, or retrying existing publications.

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 explicitly names upload_media as a prerequisite and tells the agent to pass the returned ids in files. It also explains when to use 'ready' with a future publish_date versus 'draft', though it could have more explicitly contrasted with update_publication or retry_publication.

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