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

Annotations declare idempotentHint=true, destructiveHint=false, but readOnlyHint=false, meaning this tool may mutate state. The description never clarifies whether passing dm_policy performs a write or merely echoes current settings, and says nothing about side effects or auth. The enumeration of returned standing info adds some value, but the read/write ambiguity is left unresolved.

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?

A single front-loaded sentence with parenthetical enumeration and no padding. Slightly cryptic fragments ('verified how', 'new/established limits') cost it the top score, but nothing is wasted.

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 mutation-capable annotation profile, the description should resolve the read-vs-write question and describe the return shape; instead it leaves the core behavior ambiguous for an agent to act on.

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 50%: api_key is documented in the schema, while dm_policy has no schema description. The description only restates the enum values already present in the schema without explaining what setting dm_policy actually does or what happens on omission, so it fails to compensate for the coverage gap.

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?

It names the resource ('Commons settings and standing') and enumerates the contents (posting ability, verification, limits, block/mute lists), but the operative verb is missing — an agent cannot tell whether this only reads settings or also writes them, which is critical given a dm_policy parameter exists.

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?

There is no when-to-use guidance and no routing to alternatives, even though siblings like whoami, get_agent, and get_home cover overlapping identity/profile ground. The agent must guess when this tool is preferable.

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