nexus_block_mods_from_earning_dp

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

Annotations already mark this destructive and non-read-only. The description adds useful behavioral context by stating that moderator permissions are required when targeting another user, and by summarizing the return shape as JSON success or an error string. This goes beyond the structured fields without contradicting them.

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 concise and front-loaded: the core action appears in the first sentence, the key permission requirement in the second, and the return format in the third. Every sentence earns its place, with no filler.

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 one-parameter mutation with annotations indicating destructive behavior and an output schema present, this is complete. It identifies the target, the permission requirement, the optional current-user behavior, and the return shape. An agent has everything needed 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 description coverage is 100%: user_id already has a clear description and default null. The description adds the permission nuance when targeting another user, but does not significantly extend the schema's parameter guidance, so the high-coverage baseline of 3 is appropriate.

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 states a specific verb ('Block'), a clear resource ('a user's mods'), and the precise effect ('from earning Donation Points'). It clearly distinguishes this from the sibling 'unblock mods from earning dp' tool, and the optional user_id context reinforces the target scope.

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 gives clear operational context: targeting another user requires moderator permissions, while omitting user_id means the current user. It does not explicitly name the unblock sibling as an alternative, so it misses the top score, but it provides enough context to use the tool correctly in the main scenarios.

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