Set slow-mode delay

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

With openWorldHint and idempotentHint annotations present, the description adds the behavioral detail that only non-admin posting is affected. It does not disclose permission requirements or side effects beyond the annotation coverage, so the score stays at a solid 3.

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 a single sentence plus an allowed-values list, front-loaded with the core purpose. Every word earns its place, with no redundancy or 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 simple tool with 3 parameters and no output schema, the description covers the primary behavior and the most important parameter (seconds). It omits accountId and permission prerequisites, but annotations cover idempotency and open-world context, making it reasonably complete.

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 0%, so the description must compensate. It explicitly enumerates allowed values for 'seconds', which adds meaning beyond the schema's minimum-0 constraint. 'peer' is implied as the chat where slow mode applies, though accountId remains undocumented.

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+resource: 'Limit how often non-admins can post.' This clearly explains what the tool does and distinguishes it from sibling tools that handle other chat settings like mute or notifications.

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 provides clear context for when to use this tool: when you want to restrict posting frequency for non-admins. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous and no competing sibling tool exists.

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