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

Adds substantial side-effect detail beyond the annotations: the change is member-visible, moves them on the leaderboard, and can cross a threshold that grants a Discord role. It also clarifies arithmetic behavior (subtract floors at 0, set is absolute) that would otherwise be guessed. It does not say whether losing XP revokes a previously granted role, nor whether any permission is required — a meaningful gap for a non-idempotent mutation.

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?

Compact and front-loaded: the outward effect leads, followed by side effects and semantics, with no filler sentences. The unexplained 'Outward:' label is slightly awkward but functional.

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 no output schema and a non-idempotent mutation, the description supplies the important consumer-facing consequences, arithmetic rules, and a confirmation guardrail. Missing only permission requirements, anything about returned data, and role-revocation behavior on XP loss.

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 only 33% and `operation` has no enum, so the description has to carry the meaning — and it does, naming add/subtract/set and distinguishing absolute `set` from delta semantics. `amount` bounds and signedness remain unspecified, and `member_id` is left to the schema.

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?

Opens with a precise verb set and resource: 'Add, subtract or set a member's XP.' The operation enumerations plus the XP resource make it easy to separate from siblings such as modify_accomplishments or get_xp_history, which operate on different data.

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?

Gives a concrete call-time precondition ('Confirm the number with the human before calling'), which is real usage guidance. It does not, however, state when to prefer this tool over alternatives or when it should not be used at all, so it stops short of a 5.

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