discord_admin_threads

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

Annotations already declare destructiveHint=true, so the mutation nature is known. The description adds no extra context about permissions, side effects of removing members, idempotency, or what 'update' entails. It doesn't contradict annotations but provides no behavioral transparency beyond them.

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 a single sentence, front-loaded with the primary action 'List active threads', and avoids unnecessary words. It is concise and structurally acceptable, though it could benefit from more structured elaboration of operations.

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?

With 5 parameters, 7 operations, no output schema, and sparse annotations, this description is too brief. It leaves the agent uncertain about operation-specific requirements, expected responses, and relationships to other admin tools, making the tool incomplete for complex invocations.

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 40%, and the description does not compensate. It fails to clarify the roles of userId, threadId, or data for different operations, nor how the operation enum maps to required parameters. The operation list is present in the schema, but the description adds no semantic meaning to the parameters.

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 lists active threads and manages thread membership, naming the resource and specific actions. It distinguishes from thread creation (discord_create_thread) by focusing on existing threads, though it doesn't explicitly mention alternatives. The compound nature is slightly broad but still specific enough.

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 no guidance on when to use this tool versus sibling tools like discord_admin_channels or discord_admin_members, nor does it explain operation-specific prerequisites. Usage is only implied by the stated capabilities, not explicitly directed.

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