fb_validate_pre_publish

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

Discloses network call dependency (fetch_recent, page_access_token) and details of checks (e.g., Jaccard index). No annotation support; description carries burden well, though potential side effects are not fully covered.

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?

Efficient structure: intro line, bulleted checks, parameter list. Every sentence adds value. No fluff.

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 checks, parameters, return value. Given no annotations and 0% schema coverage, description is thorough. Minor omission: no details on error handling or exact output dict keys.

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?

With 0% schema coverage, detailed parameter descriptions compensate fully: values, defaults, purpose (e.g., fetch_recent 'Set False to skip network'). Adds meaning beyond 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?

Clear verb+resource: validates pre-publish. Lists four specific checks, differentiating from sibling tools like fb_anti_duplicate_check which only performs one check.

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?

Explicitly states 'BEFORE publishing', giving clear usage context. Describes optional fetch_recent behavior, but doesn't explicitly contrast with siblings or state when not to use.

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