soundboard_create_guild_sound

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

Annotations provide only generic hints (readOnlyHint=false, openWorldHint=true). The description adds meaningful constraints (base64 data URI, max 512 KB raw) and return shape, which helps, but it doesn't disclose permissions, rate limits, or failure behavior. It carries some burden beyond annotations but not exhaustively.

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 brief, well-structured with bold labels, and every sentence adds value: purpose, key constraint, and return. No fluff or repetition.

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 7-parameter schema, output schema, and annotations, the description adequately covers the most complex parameter (sound) and expected returns. It doesn't discuss errors or prerequisites, but the essential details are present. It could mention alternatives to sibling tools, but that overlaps with usage guidelines.

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 covers all 100% of parameters, but the description adds the crucial 'max 512 KB raw' constraint on sound not present in the schema. It also summarizes the return object, reinforcing parameter meanings. This goes beyond the baseline for full schema coverage.

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 'Upload a new soundboard sound to a guild' with a clear verb and resource. It naturally distinguishes from siblings like soundboard_modify_guild_sound and soundboard_delete_guild_sound by emphasizing 'new'.

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 purpose implies when to use it (creating a new sound), but it doesn't explicitly compare to alternatives like modify or delete. There's no 'when not to use' or mention of sibling tools, so guidance remains implied.

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