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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, but the description adds valuable behavioral context beyond that: the locking mechanism ('after the first answer locks the question'), the specific idempotency condition ('Identical normalized configuration is safe to retry'), and the rejection of changed locked configuration. It also clarifies side effects by stating it does not write answers or change members. This significantly enriches the agent's understanding of the tool's behavior.

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 three sentences, front-loaded with purpose, then permission, idempotency, return values, and side effects. Every sentence carries essential information with no filler. The structure is logical and efficient.

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?

Given the existence of an output schema (which covers return values) and the presence of annotations, the description covers key aspects: permission, idempotency, side effects, and the return of canonical_url and review_url. The main gap is the lack of parameter explanations, but for a configuration tool with moderately self-explanatory parameter names, it is fairly complete. A slight deduction for not elaborating on feedback_type or the exact meaning of 'context'.

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. However, it only vaguely mentions 'question/context' and does not explain parameters like list_id, list_name, description, or feedback_type. While some parameter names are self-explanatory, feedback_type and description could have ambiguous meanings. The description provides minimal semantic guidance for parameters beyond what the names imply, leaving the agent to guess.

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 uses a specific verb ('Configure') with a clear resource ('a list's review question/context') and a temporal scope ('before human answers begin'). It also explicitly distinguishes itself from other actions by stating what it does not do ('Does not write answers or change members'), which helps differentiate it from siblings like add_to_list or update_list.

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 states when to use it ('before human answers begin') and the permission requirement ('Requires edit access'). It also explains idempotency behavior, which guides retries. However, it does not explicitly name alternative tools or say when not to use it, though the purpose is clear enough that an agent can infer appropriate usage from context.

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