publicar_facebook

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

No annotations are provided, so the description carries the full burden. It discloses the scheduling feature and time constraints. However, it does not mention authentication needs, rate limits, or behavior when a link is provided. It lacks completeness on behavioral traits.

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 concise with two sentences. The first sentence immediately states the purpose, and the second adds scheduling details. Every word is informative without repetition.

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?

Given the lack of annotations and output schema, the description leaves gaps. It does not mention required permissions, return values (e.g., post ID), or how the link parameter affects the post. For a Facebook API tool, this is insufficient.

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 low (33%). The description adds meaning to the scheduledPublishTime parameter by specifying the valid time window. It does not elaborate on the message or link parameters, which remain under-documented.

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 the verb 'Publica en la Página de Facebook de Niveals', specifying the resource and action. It implicitly distinguishes from sibling tools like publicar_instagram and listar_posts_facebook by focusing on Facebook posting.

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?

Provides a specific guideline about scheduling with scheduledPublishTime and its constraints (10 min to 6 months). However, it does not explicitly state when to use this tool versus alternatives, nor does it exclude other scenarios like listing posts.

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