Get orphan

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

No annotations are provided, so the description carries the behavioral burden. The verb 'Get' conveys a non-mutating read operation, and the documentation link adds useful external context. However, the description does not disclose error behavior, id format expectations, or any special orphan cleanup semantics beyond the bare operation.

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 focused sentence followed by a documentation link. Every element earns its place: the sentence states the operation and scope, and the link provides supplementary context without bloat.

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 simple get-by-id operation with one parameter and no output schema. The description is sufficient for an agent to select and invoke the tool correctly; the external docs link fills any deeper context about orphaned data cleanup. It does not describe the return structure, but that is not necessary for 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?

Schema description coverage is 0%, so the description should compensate. The phrase 'by id' confirms the id parameter selects the orphan record, which is somewhat helpful, but it adds little beyond the schema's own property name 'id' and the tool name. There is no extra detail on id format or accepted values.

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 ('Get'), names the exact resource ('orphan record'), and scopes the operation to a single record identified by id. This clearly distinguishes it from sibling tools like orphan_list and other getters by specifying the object type and uniqueness.

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 clearly implies usage: call this when you have a specific orphan record id and want that one record. It does not explicitly name alternatives such as orphan_list for enumeration, but the 'single ... by id' phrasing gives sufficient contextual guidance for this simple tool.

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