list_amplification_posts

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 pagination support, which is a key behavioral trait. However, it does not mention response format, ordering, or potential side effects, though as a list operation it is likely read-only and non-destructive.

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 a single sentence that is front-loaded with the tool's purpose and key detail (pagination). Every word is necessary, and no extraneous information is included.

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?

While the description and schema cover the parameters adequately, the tool lacks an output schema and the description does not explain what an 'amplification post' contains or the response structure (e.g., pagination metadata). For a list operation, some additional context on response format would improve completeness.

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%, meaning all five parameters have descriptions in the input schema. The description adds minimal value beyond stating pagination support, which is already covered by the schema's page and per_page descriptions. Baseline score of 3 applies.

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 tool lists amplification posts (posts queued for team amplification) and supports pagination. It is distinct from sibling tools like get_amplification_post, create_amplification_post, and delete_amplification_post, which handle single post operations.

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 usage for listing posts with pagination but does not explicitly state when to use this tool over alternatives like get_amplification_post for individual posts. No exclusions or when-not-to-use guidance is provided.

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