List soundboard sounds

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

The readOnlyHint annotation already indicates a safe read operation, but the description adds no additional behavioral context such as what is returned, whether all custom sounds are listed, or how the optional 'guild' parameter affects behavior.

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 very brief, but it is a noun phrase fragment rather than a complete sentence. It is not verbose, but the brevity comes at the cost of clarity, making it under-specified.

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 no output schema and minimal annotations, the description should explicitly state that it returns the custom soundboard sounds or lists them. It does not, leaving the behavior and return value ambiguous.

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 description coverage is 100% for the single optional parameter 'guild', which already explains its purpose. The description adds no further parameter-related meaning, so the 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 'Custom soundboard sounds in the server.' identifies the resource but lacks an explicit verb such as 'list' or 'retrieve'. It is not a complete sentence and relies on the name/title to convey the action.

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?

No guidance is provided on when to use this tool or how it differs from sibling tools like create_soundboard_sound, update_soundboard_sound, or delete_soundboard_sound. The intended usage is only implied by the name.

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