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

Goes beyond the annotations (destructiveHint, idempotentHint, openWorldHint) by disclosing partial-update semantics, credential/permission behavior for review-mode tokens, and the required scopes posts:write and posts:publish. It does not clarify whether omitted fields are left intact versus cleared, which is the key ambiguity for a destructive partial update.

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?

Three tightly-packed sentences with zero filler; the patch instruction and the permission caveat are both front-loaded and each sentence carries distinct information.

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 mutation tool with no output schema and only 1 required parameter, the description covers authorization, patch semantics, and credential-mode limitations well. The remaining gaps are the return shape and whether field omission preserves or clears existing values.

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 only 50% (postId, ruleId, message are documented; enabled, replies, keywords are not). The description compensates by mapping prose to parameters and clarifying that 'enabled' toggles the rule on/off, but it adds no format, constraint, or null-handling detail for the replies/keywords arrays. Roughly baseline for half-covered schema.

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?

States a specific verb ('Changes') on a specific resource ('a rule') and enumerates the mutable fields (keywords, replies, private message/post, enabled). The verb 'changes' cleanly separates it from create_autoreply and delete_autoreply without needing to name them.

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?

Gives real when-to/when-not guidance: 'Send only what changes' establishes patch semantics, and the review-mode paragraph spells out exactly which operations a restricted credential may and may not perform ('may turn a rule off... may not turn one on or change one that is live'). It also names the required scopes. It stops short of naming sibling alternatives like create_autoreply/delete_autoreply explicitly.

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