soundboard_list_guild_sounds

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds value by detailing the return shape and warning about raw, untrusted names, which is useful context beyond the 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 highly concise, split into two short labeled sections. It front-loads the purpose and provides return information in a compact, structured format with no wasted 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?

Given the simple single-parameter tool, strong annotations, and existing output schema, the description is complete. It even adds helpful details about untrusted names and return structure, so no important context is missing.

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 has 100% coverage with a clear description for guild_id. The description does not need to add further parameter detail; the schema fully explains the only parameter.

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 states 'List a guild's custom soundboard sounds' with a specific verb and resource. It clearly distinguishes from sibling tools like soundboard_list_default_sounds by specifying 'custom' and 'guild's'.

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 clear context: this tool lists a guild's custom sounds. It does not explicitly name alternatives or exclusions, but the purpose is sufficiently clear to differentiate from default soundboard lists and individual sound retrieval.

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