discord_update_membership_screening

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds useful behavioral context beyond those annotations: 'Only provided fields change' clarifies partial-update semantics, prerequisites are disclosed, and 'Returns the updated form' tells the agent what to expect despite the absence of an output schema.

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?

Two sentences with no filler: the action and target are front-loaded, followed by the partial-update caveat, prerequisites, and return value. Every sentence earns its place.

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 an update tool with three parameters, one required, and no output schema, the description is complete. It covers what updates, what changes, what prerequisites are needed, and what is returned. The only remaining nuance, that form_fields replaces existing rules, is already present in the input schema.

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 100%, so the schema already documents each parameter. The description summarizes the meaning of description and form_fields, but does not add syntax, formatting, or replacement semantics beyond what the schema already provides. The baseline of 3 applies here.

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 names a specific verb and resource: 'Update the server's membership screening form' and explicitly identifies the two things it sets: 'welcome description' and 'rules new members must agree to.' This clearly distinguishes it from the sibling discord_get_membership_screening, which reads the same resource.

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 implies when to use the tool (to modify the membership screening form) and provides important prerequisites: the Community feature and Manage Server permission. However, it does not explicitly mention alternatives such as discord_get_membership_screening for reading the current form, nor does it state when not to use this tool.

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