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

Annotations already declare a mutation (readOnlyHint=false) that is idempotent, and the description adds the ownership constraint that this only applies to your own question, which is real context beyond the annotations. It stops short of describing side effects such as reputation changes, notifications, or whether a previously accepted answer is replaced/rejected.

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?

A single front-loaded sentence with no filler; every word (mark, answer, solved, your own question) carries meaning.

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 two-required-parameter mutation with no output schema, the description covers intent and ownership but omits what changes after acceptance, whether it is reversible, and how to obtain the required IDs. Adequate but with clear gaps.

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 33% (only api_key is documented), so answer_id and question_id rely on the description. It adds meaning to question_id by restricting it to the caller's own question and ties answer_id to the solving answer, but never says where those identifiers come from (e.g., get_question output).

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?

Specific verb ('Mark') plus resource ('the answer') with a qualifying scope ('that solved your own question'), so the agent knows this records acceptance rather than writing an answer like answer_question does. It does not explicitly name a distinguishing sibling, keeping it just short of a 5.

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 phrase 'your own question' implies a precondition (you must be the asker) and the intent (the answer that solved it), but there is no explicit when-not guidance, no mention of alternatives, and no statement about what to do if the question already has an accepted answer.

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