discord_find_permission_problems

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

Annotations already declare readOnlyHint=true, and the description's enumeration of exactly which conditions constitute a 'problem' (invisible channels, @everyone lockouts, public-channel Send Messages denies, foreign Administrator roles, hierarchy overreach) is substantive behavioral disclosure of scan scope. It stops short of noting cost, rate limits, or that a full scan may be slow across large guilds.

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?

One dense sentence plus a two-word safety tag; the headline purpose is front-loaded before the enumeration. Slightly long but nearly every clause carries distinct information (the five detection categories), so little is wasted.

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 a single required param, an output schema, and readOnly/openWorld annotations, the description only needs to explain what the scan looks for, which it does thoroughly including the 'returns a fix' promise. Missing only operational context such as required bot permissions or scanning scope/time.

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?

Only one parameter, guild_id, and schema description coverage is 100% with a documented snowflake pattern, so the schema already carries the semantics. The description adds nothing about the parameter; baseline 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?

Specific verb+resource ('scan a server for permission problems') followed by an explicit enumeration of the five problem classes it detects, which goes well beyond restating the name. It is clearly distinguishable from narrower siblings like discord_explain_permissions, though it never names the sibling it might be confused with (discord_audit_permissions).

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 use case (diagnostic scan of a whole guild) is implied by the enumeration of checks, but there is no explicit guidance on when to prefer this over discord_audit_permissions or discord_explain_permissions, nor any prerequisites (bot must be a member, admin scope needed).

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