Get the lineage tree (parents + children) for an item. Item member access.

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds 'Item member access,' which vaguely suggests authorization requirements but does not specify permissions or behavior on failure. No details about return structure or side effects are provided.

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 very concise at two sentences, with no redundant information. However, it is overly terse and lacks front-loading of critical details like usage context or parameter descriptions. Every sentence earns its place but misses necessary elaboration.

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 no output schema and two parameters, the description is incomplete. It does not describe the returned lineage tree structure, how parents/children are represented, or any limits on depth. The phrase 'Item member access' is ambiguous and insufficient for understanding authorization context.

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 must explain both parameters (x-api-key, item_id). However, it provides no details beyond the tool's purpose. The required item_id parameter is not clarified, and the optional x-api-key is ignored.

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?

Tautological: description restates name/title.

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 guidance on when to use this tool versus alternatives (e.g., items.get, items.search). The description lacks any contextual hints about prerequisites or limitations, such as whether it requires item member access as implied by the phrase 'Item member access'.

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