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

Beyond the annotations, the description discloses important behavior: an author's answer is reported to the reviewer, 'fixed: false' leaves the remark standing and causes the next edit to ask again, and 'reopen'/'withdraw' are reviewer-only actions. These details clarify permissions and state transitions that the annotations alone do not provide.

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 compact and front-loaded: it states the purpose first, then explains author versus reviewer semantics in a dense but purposeful way. Every clause adds operational meaning, with no redundant restatement of the title or schema.

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, the description covers the necessary context: who may call it, what each response mode does, and how the reviewer is notified. No critical behavioral information appears to be missing for correct invocation.

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 100%, so the schema already defines the parameters, but the description adds meaningful semantics for the role-specific use of 'fixed', 'action', and 'note'. It clarifies that 'fixed: false' is compared against the current version and that reopening/withdrawing are reviewer actions, though it does not further elaborate on 'remarkId'.

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 opens with a specific verb and resource: 'Answer a remark of a page's review.' It also points to the sibling tool get_wiki_page_reviews, making the distinction between finding remarks and responding to them clear without requiring schema comparison.

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?

It explicitly explains role-based usage: page authors use 'fixed' to indicate whether a remark was resolved, while reviewers or project leads use 'action' to reopen or withdraw a remark. This gives clear conditions for selecting each parameter path and names the related sibling tool for retrieval.

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