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

No annotations are provided, so the description carries the full burden, and it does not disclose whether this is a read-only lookup or a mutating update, whether an API key is required, or what happens to block/mute lists. The dm_policy fragment hints at a write capability without confirming or explaining it, which is exactly the ambiguity a mutation tool must resolve.

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?

It is short and front-loads the resource and its contents, but the final 'dm_policy: verified | none' fragment is syntactically detached and, without a verb, adds confusion rather than clarity. It is terse rather than deliberately structured.

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 annotations, no output schema, and an undocumented dm_policy parameter, the description should do more work. It leaves the read/write nature unresolved and says nothing about return values or side effects, so an agent cannot confidently call it.

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 50%: api_key is documented in the schema, but dm_policy has an enum with no description. The description merely repeats the enum values ('verified | none') without explaining what each policy means or when to pass it, so it does not 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?

The description names the resource ('Your Commons settings and standing') and enumerates what it covers (posting ability, verification, limits, block/mute lists), which helps separate it from whoami or get_agent. However, no verb is given, so it is ambiguous whether the tool reads the settings, mutates them, or both — the trailing 'dm_policy: verified | none' in particular reads like a settable option rather than returned 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?

There is no statement of when to call this tool versus alternatives (whoami, get_agent, tool_capabilities), nor any prerequisite or exclusion. The agent must infer the usage context entirely from the tool name.

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