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

No annotations are present, so the description carries the full burden. It discloses that the response contains 'nodes and typed edges' with examples, which is useful. But it does not clarify whether traversal is one-hop or multi-hop, what limits or pagination exist, or how missing entities are handled, leaving several behavioral traits implicit.

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?

Two sentences with no fluff. The first defines the tool at a high level with concrete edge-type examples; the second gives a practical usage scenario. Every phrase earns its place.

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?

For a two-parameter tool with no output schema, the description covers the essential information: what the tool returns, how to invoke it, and a canonical use case. Minor gaps remain, such as traversal depth, explicit support for non-company entity types, and id format, but these are not blocking for correct invocation.

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?

With 0% schema description coverage, the description is the only source of parameter meaning. It helps by framing id as an entity identifier and entity_type as the starting entity type (e.g., 'a company'), and it gives examples of target relationship types. It doesn't document every enum value or id format, but the enum in the schema and these examples provide meaningful guidance.

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 states a specific operation — 'Knowledge-graph neighborhood of an entity' — and uses the verb 'traverse' with concrete destination examples (exchange, jurisdiction, funds, peers). It also names edge types (lists_on, domiciled_in, managed_by, sector_peer), which clearly distinguishes it from sibling tools like search or lookup that are not graph traversals.

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 includes an explicit use-case directive: 'Use to traverse from a company to its exchange, jurisdiction, funds and peers.' This gives clear context for when to use the tool. However, it does not explicitly mention alternatives or state when not to use it, so it lacks full exclusionary guidance.

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