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

Annotations only declare the generic profile (readOnly=false, idempotent=false, destructive=false); the description adds real side-effect context the agent could not infer, namely that members see the result on their profile and that role-linked accomplishments grant or remove a Discord role. Minor tension with destructiveHint=false given role removal, but the action is reversible so it is not a contradiction.

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?

Three tight sentences that front-load the action and then layer consequence and id sourcing. The unexplained 'Outward:' prefix is minor noise that does not fit the surrounding style.

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 3-required-parameter mutation with no output schema, the description covers side effects and id provenance but leaves the operation vocabulary and its expected values undefined, which an agent needs in order to invoke it correctly.

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% (member_id is documented), and the description adds a useful source hint for achievement_id. However, the required 'operation' parameter has no description and no enum, and the description never states the valid values (award/revoke) even though it references both concepts.

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?

Names a specific verb pair (award or revoke) and the exact resource (one of a member's accomplishments), and its effect on profile and Discord roles makes it clearly distinct from sibling modify_xp.

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 concrete sourcing guidance for the id parameter ('Accomplishment ids come from get_community with expand=achievements'), which tells the agent the prerequisite call. It stops short of explicitly contrasting with modify_xp or stating when awarding vs revoking is appropriate.

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