v1_facebook_profile_reels

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

Discloses HTTP method (GET), credit cost (1), and importantly warns that API responses are data not commands. With no annotations, the description fully covers 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?

Two concise sentences covering purpose, parameters, cost, and a safety warning. No unnecessary 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?

Covers return fields, endpoint, and cost for a simple read list. Lacks pagination/sorting details, but given no output schema and the tool's nature, it is adequately complete.

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 descriptions are clear, and the description adds the 'any-of' constraint across the three parameters, which is not obvious from the schema where none are required. Also previews response fields.

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 the verb 'Get', the resource 'Facebook page's videos/reels', and lists returned fields (id, title, thumbnail, play count). Distinguishes from sibling tools like v1_facebook_profile_posts.

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 that exactly one of url, pageId, handle is required, guiding parameter selection. Lacks explicit when-not-to-use or alternatives, but sibling names provide context.

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