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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that the scores become 'ruling inputs', but it never says whether existing scores are replaced or merged, what the idempotentHint=false implication means in practice, or what preconditions the case must satisfy.

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 or redundancy. Its brevity is close to under-specification, but nothing in it is wasted.

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?

This is a mutating tool with a nested object parameter inside a multi-step case workflow, and the description omits preconditions, overwrite semantics, and its place relative to rule and verify_ruling. An output schema exists, so return values need not be explained, but the call-time context is still thin.

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 carries the burden, and it does partially compensate by explaining that scores maps a party to a value in [0,1]. The case_id parameter is left entirely unexplained, and the format of the 'party' key is not specified.

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 verb 'Attach' and resource 'trust-oracle reputation scores' give a rough sense of the operation, and the parenthetical '(party -> [0,1])' clarifies the data shape. However, the phrasing is jargon-heavy and does not distinguish this tool from workflow siblings such as rule, submit_evidence, or verify_ruling, which also feed a case's ruling inputs.

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?

There is no when-to-use guidance, no prerequisite state for the case, and no mention of alternatives. An agent cannot tell from the description whether this must be called before verify_ruling, whether it can be called repeatedly, or when trust scores should be supplied at all.

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