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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the safety profile is covered. The description goes beyond them by stating the real-world impact ('changes future visitor-facing answers') and the additive/non-destructive scope ('never edits or deletes existing training'). The duplicate-suppression sentence largely restates idempotentHint, which is why this is a 4 rather than a 5.

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?

Five short sentences, front-loaded with the action and effect, followed by preconditions and then boundaries. Nothing is redundant padding: each sentence either states scope, a precondition, or a behavioral limit.

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?

An output schema exists, so return values need not be explained. The description covers effect on future answers, the pre-call verification step, and the non-destructive/idempotent boundaries, which is everything an agent needs to invoke a 3-parameter write tool correctly.

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 100%, so the schema already documents question, answer, and category with lengths and examples. The description reinforces that text must be user-approved but adds no format, syntax, or constraint detail beyond what the schema supplies — the baseline 3 for a fully documented 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?

Specific verb+resource: 'Add a user-approved question/answer pair to this workspace's SuperBot training.' It names the object (training entry), the required input shape, and even the sibling tool (search_knowledge) that an agent might confuse it with, so it is separable from the read-oriented siblings without opening a schema.

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?

Explicit preconditions and routing: 'Confirm the exact text with the user and check search_knowledge first,' plus an exclusion ('never edits or deletes existing training'). This tells the agent both when to call it and what it cannot be used for, which is exactly the guidance a write tool needs.

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