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

With readOnlyHint=false, the description adds real value: ambiguous input returns needs_confirmation and does not overwrite a saved policy, the source sentence is not stored (privacy), and it requires the same API key as /mcp. It still doesn't spell out what a successful write does to the previously saved policy beyond the negative case.

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?

Four short sentences, front-loaded with the cost and the core transformation, then the ambiguity and privacy caveats. 'Free.' as an opener is unusual but informative; no sentence is filler.

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?

No output schema exists, so the description carries the return burden and does so adequately by naming the output fields and the needs_confirmation path. The exact success response shape (confirmation vs. echoed weights) remains slightly underspecified.

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% and the single parameter is documented as an owner sentence with max 500 chars. The description adds semantics the schema lacks — what the sentence is parsed into and how ambiguous text is handled — which meaningfully compensates.

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+resource framing: it turns one owner sentence into trust_weight, cost_weight, and max USD per call, which tells an agent exactly what the tool produces. It doesn't explicitly contrast with siblings rank_tools_for_task or record_outcome, but the transformation is distinct enough to be recognizable.

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?

'Free.' and the ambiguity/needs_confirmation behavior imply this is a low-risk setup step, but the description never states when to call it versus the sibling tools or what prerequisites exist beyond the API key. Usage is inferable rather than stated.

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