get_xrefs_from

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the purpose. It does not state that the operation is read-only, how results are ordered, what happens for an address with no references, or how pagination (limit/offset) behaves.

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 wasted words; the verb and scoping constraint appear immediately.

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?

An output schema exists so return values need not be described, and the tool is a simple query. Still, with no annotations and no pagination or direction-vs-sibling explanation, the definition is only minimally complete for the agent to invoke it confidently.

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 schema titles ('Limit', 'Offset', 'Address') add little. The description clarifies that the address may be an instruction or data address, which is useful, but it says nothing about the limit/offset pagination parameters.

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?

States a specific verb ('List') and resource ('references from a single instruction or data address') with clear scope. It is distinguishably about outgoing references, though it does not explicitly name the sibling get_xrefs_to to sharpen the direction contrast.

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 word 'from' implicitly contrasts with the sibling get_xrefs_to, so the usage direction is inferable. However, there is no explicit when-to-use guidance, no mention of when to prefer get_function_xrefs, and no prerequisites for the address argument.

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