create_post

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

No annotations, so description must disclose all behavioral traits. Only mentions post types and return ID. Lacks details on side effects, authorization needs, rate limits, or error handling. Insufficient for a 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?

Two sentences, 19 words, front-loaded with action and resource. No wasted words.

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?

Tool is straightforward with 4 non-required parameters. Output is simple (post ID). Context is mostly complete, but missing behavioral transparency details.

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?

Input schema has 4 parameters with 100% description coverage. Description adds grouping by post types (text, link, photo), which is marginal added value over 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?

Clearly states action (create), resource (post on Facebook Page), supported types (text, link, photo), and return value (new post ID). Distinguishes from read-only sibling tools.

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?

No explicit when-to-use or when-not-to-use guidance. Siblings are all read-only, so usage is intuitive, but no prerequisites or permissions mentioned.

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