promote_admin

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

With no annotations, the description carries full burden. It explains that demote=True revokes all admin rights and lists individual permission parameters. However, it lacks details on permissions required to use the tool, error states (e.g., user already admin), or side effects like automatic notification.

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: a summary sentence followed by a list of parameter explanations. It is front-loaded with the core action. The parameter list could be more compact, but overall it is well-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?

The description covers parameter semantics adequately but omits key behavioral details like required permissions, error handling, or output expectations (despite an output schema existing). For a tool with 14 parameters, more contextual guidance (e.g., typical use cases) would improve completeness.

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 0%, so description must explain all 14 parameters. It does so by providing short Chinese explanations for each (e.g., 'title: 自定义头衔' for custom title). The description adds meaning beyond the schema, though default values are not explicitly restated.

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 clearly states the tool's core action: promoting a user to admin or revoking admin status via the demote parameter. It uses specific verbs and resource (管理员权限), distinguishing it from sibling tools like restrict_participant or set_default_permissions.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., restrict_participant for limited privileges). No prerequisites or context for when demoting or promoting is appropriate.

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