discord_admin_server

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

The description adds minimal behavioral context beyond the annotations. It doesn't specify which operations are destructive, permission requirements, or side effects of pruning. Annotations already flag destructiveHint=true, but the description fails to elaborate on what destruction occurs or when.

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 concise sentence with no wasted words. However, it is under-specified, sacrificing completeness for brevity, but it still earns a high score on conciseness due to its efficient structure.

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 5-parameter tool with four distinct operations, including destructive prune, the description is inadequate. It doesn't explain the full scope of operations, return values, or when to use this over other admin tools, and there is no output schema to fill the gaps.

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 coverage is low (40%), and the description provides no parameter semantics. The meaning of 'data', 'days', and 'includeRoles' is entirely unclear, and the description doesn't compensate for the schema's missing details.

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 identifies the tool as reading or modifying the configured Discord server's settings, with a specific verb and resource. However, it omits the prune operations visible in the schema and doesn't distinguish this from sibling tools like discord_get_server or discord_admin_request.

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 versus alternatives. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer from the operation enum.

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