discord_onboarding

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

With no annotations, the description carries the full burden. It mentions that Discord enforces Community onboarding constraints, implying validation, but fails to disclose whether 'update' is destructive, what authorization is required, or what happens on success/failure. The mutation behavior is inadequately described.

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 short and front-loaded, but it is underspecified. The first sentence states the purpose; the second adds a constraint note. While concise, it wastes the opportunity to add critical details, making it merely acceptable rather than well-structured.

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 tool's complexity (5 params, no output schema, no annotations, mutation possible), the description is severely incomplete. It omits the meaning of 'action', the structure of 'body', the role of 'dryRun', and any return-value behavior. The single constraint remark is insufficient.

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 0% and the description does not clarify any of the 5 parameters (guildId, action, body, dryRun, reason). The word 'onboarding configuration' hints at 'body' but gives no concrete meaning for the parameters, leaving the agent to guess.

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 operates on 'guild onboarding configuration' with verbs 'Get or replace', distinguishing it from sibling tools like discord_welcome_screen or discord_modify_guild. However, 'replace' is not exactly the same as the 'update' action in the schema, introducing slight ambiguity.

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 'get' versus 'update', nor when this tool is preferable to other guild-modification tools. The constraint note is informative but does not give actionable usage criteria.

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