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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's safety profile is covered. The description adds useful behavioral context about traversing an ownership chain and flagging specific hop types, but it does not disclose output behavior, depth boundary effects, or data-source limitations. This is acceptable but not rich given the available annotations.

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 a single, front-loaded sentence with no wasted words. The em-dash phrase adds a clear investigative framing. It could be slightly more informative, but it is concise and readable.

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 that there is no output schema, no parameter descriptions, and the tool performs a potentially complex graph walk with sanctions and jurisdiction flagging, the description is incomplete. It does not explain what the returned result contains, how max_depth affects traversal, whether cycles are handled, or how it relates to get_sanctions and trace_ownership_path.

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%, and the description does not explain the required 'id' parameter or the optional 'max_depth' parameter. The phrase 'Walk the ownership chain' implies that 'id' is the starting point, but 'max_depth' is completely unmentioned and no formats, defaults, or limits are given. The description fails to compensate for the absent schema descriptions.

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 phrase, 'Walk the ownership chain and flag sanctioned + secrecy-jurisdiction hops,' which clearly identifies the tool's core function. It also orients the user with the outcome label 'offshore-layering lead,' distinguishing it from sibling tools like trace_ownership_path or get_sanctions, though it does not explicitly name these alternatives.

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?

The description implies usage for offshore-layering investigation by mentioning 'sanctioned + secrecy-jurisdiction hops,' but it does not explicitly state when to use this tool versus sibling tools such as trace_ownership_path or get_sanctions. No when-not-to-use guidance or alternative tool references are provided.

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