soundboard_list_default_sounds

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond annotations by detailing the return structure and specifically noting that 'Names remain raw Discord data; untrusted_names provides a separately fenced copy,' which informs the agent about data trustworthiness and output nuance.

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 extremely concise, with two clear sections: Purpose and Returns. It front-loads the core function and then efficiently describes the return payload, with no redundant or filler content.

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 zero-parameter list tool with rich annotations and an output schema, the description fully covers the essential context. It explains the return shape and the special handling of untrusted names, which is sufficient for an agent to select and invoke the tool correctly.

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 tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description adds no parameter information, but none is needed; it instead focuses on the return format, which is appropriate.

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 function: 'List Discord-provided default soundboard sounds (available globally).' This specifies the verb 'list', the resource (default soundboard sounds), and the scope ('globally'), effectively distinguishing it from sibling tools like soundboard_list_guild_sounds.

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 context through 'Discord-provided default' and 'available globally', making it clear this is for platform-wide sounds rather than guild-specific ones. However, it does not explicitly name alternative tools for guild sounds, so there is clear context but no direct exclusion or alternative mention.

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