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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the bar is lower; the description usefully confirms 'saves nothing' and names the two possible returns (a shortcut payload to save, or a link where an instruction is added). It does not explain what happens on a rejected/duplicate instruction, or why a mutation-grade idempotency key appears in a read-only tool.

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 short sentences, front-loaded with the core behavior and the no-save guarantee; the credits note is a slight tangent but short and decision-relevant. No wasted clauses.

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?

With no output schema, the description carries the return-value burden and does so by naming both outcomes. For a nested-input tool with 75% schema coverage this is close to sufficient; what's missing is failure behavior when the statement conflicts with existing Knowledge entries.

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 75%, so baseline is 3. The description does add real meaning to the `kind` enum by glossing 'durable instruction' versus 'reusable request (shortcut)', but says nothing about `command`, `accountIds`, or `userStatement`, which carry the remaining ambiguity.

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 and resource: it checks a person's stated instruction or shortcut against what Knowledge already holds, and explicitly clarifies that it is a validation step, not a save. That distinguishes it from knowledge_manage (named as the save path) and from knowledge_skills, though the sibling it names is not in the provided sibling 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?

Clear sequencing guidance: call this first, then only after the person says yes use knowledge_manage to persist. It also gives a cost reason to prefer it (free, no Adrails credits). It does not state when NOT to use it (e.g. when the instruction is already saved, or when no user has confirmed).

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