discord_create_thread

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

Annotations already provide readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds meaningful context: the thread is public and local write permission is required, which goes beyond structured fields.

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?

Exactly two sentences: the first states the purpose, the second a key precondition. No redundant words or filler.

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?

No output schema exists, so the description should explain what happens on success or failure. It lacks parameter guidance and error conditions. For a three-parameter create tool, this is too sparse to be fully actionable.

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 only 33% (only channelId has a description), so the description must compensate. It does not mention name constraints, autoArchiveMinutes allowed values, or how channelId relates to 'allowed text channel.' No parameter semantics are clarified.

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 'Create a public thread in an allowed text channel,' a specific verb + resource + constraint. It differentiates from sibling tools like discord_send_message and discord_admin_threads by specifying 'public thread' and channel authorization.

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 gives context by saying 'Writes must be enabled locally' and 'allowed text channel,' implying when the tool can be used, but it does not explicitly name alternatives or exclusions. Usage guidance is implied rather than stated.

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