Get Blocked Users

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Lists' is consistent with those. The description adds no further behavioral context such as pagination, returned fields, or permission requirements, but the annotation coverage mitigates this gap.

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: one sentence states the core behavior, followed by a minimal args block. There is no filler or redundant 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?

For a simple read-only list with one required parameter, the definition is minimally sufficient: page_id is documented, response_format is covered by the schema, and annotations confirm safety. However, there is no output schema or description of the return shape, so an agent cannot anticipate what fields or pagination behavior to expect.

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?

The description adds mild value by clarifying page_id as 'Facebook Page ID', which is not in the schema. response_format is omitted from the description, but the schema provides a full explanation and a default, partially compensating for the low schema description coverage.

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 uses a specific verb 'Lists' and a clear resource 'users blocked by the Facebook Page'. This makes the operation unambiguous and distinguishes it from related sibling tools such as meta_block_user.

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 intended use is implied: call this when you need the list of users blocked by a Facebook Page. However, there is no explicit guidance about when not to use it, prerequisites, or comparisons to alternatives.

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