Profile Posts

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

Adds substantial behavior beyond the annotations: a 3-post-per-page API ceiling, paid-credit consumption, a mandatory confirm=true, and a reconciliation of why a read operation is annotated readOnlyHint=false (read-like POST that does not publish). This is exactly the kind of context annotations cannot convey.

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?

Front-loads the core purpose, then the per-post field list, parameter choice, and cost caveat. Dense but every sentence carries information; the field enumeration is slightly verbose but useful given no output schema.

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?

With no output schema, the description supplies the return shape (id, text, url, counts, publishTime, videoDetails URLs, topComments) and the pagination limit, plus the credit/confirm requirement. Nothing needed to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds value by noting url and pageId are alternatives and that pageId is faster. It does not restate the confirm/cursor semantics, which the schema already covers.

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?

States a specific verb and resource (returns publicly visible Facebook profile posts) with clear scope, and the enumerated return fields distinguish it from siblings like facebook_profile and facebook_post. An agent can tell what this returns without opening the schema.

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 the usage context (fetch a profile's posts) and gives a parameter-choice hint ('pageId is faster'), but names no alternatives and states no when-not conditions versus facebook_profile_posts-adjacent tools. Usage is implied rather than defined.

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