stickers_list_guild

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

The description goes beyond the annotations by specifying the return shape and noting that the 'description' field is omitted from list output, suggesting retrieval via stickers_get_guild_sticker for that detail. This adds behavioral context without contradicting the readOnly/destructive annotations.

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 well-structured with clear sections: Purpose, When to use, and Returns. It is concise, front-loaded with the core purpose, and every sentence adds value without redundancy.

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 list tool with one parameter and an output schema, the description covers the essential aspects: purpose, usage, and a notable return behavior (omission of description). It could potentially mention pagination or sorting, but this is not strictly necessary and the given details are adequate.

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 input schema already provides 100% coverage for the only parameter (guild_id) with the description 'Guild to inspect'. The tool description does not add additional parameter-level semantics, so the baseline 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's purpose: 'List custom stickers belonging to a guild.' This uses a specific verb (List) and resource (custom stickers in a guild), and it distinguishes from sibling tools like stickers_list_packs and stickers_get_guild_sticker by focusing on guild stickers. The 'When to use' section reinforces the purpose.

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 provides a clear usage context ('Inventory guild stickers; pick one for a message') under 'When to use'. It does not explicitly mention when not to use the tool or alternative tools, but the context is sufficiently clear for an agent to decide when to invoke it.

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