find_xrefs_hex

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

Discloses the types of references searched and return format. With no annotations, it does a good job but lacks details on error handling or constraints like maximum hex size.

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?

Well-structured with a summary line followed by details. Every sentence adds value, no fluff.

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?

Covers all inputs and return type. With an output schema present, it doesn't need to detail return values. Lacks error handling info but adequate for a tool with clear purpose.

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?

The description includes a docstring with Args that explains each parameter (hex_code, target_address, arch, base_address) beyond the schema, which has 0% description coverage.

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?

Clearly states it finds cross-references to a target address in hex-encoded machine code, listing specific reference types (call, jump, etc.). This distinguishes it from siblings like find_xrefs_in_file which works on files.

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?

Implies usage for hex machine code snippets but does not explicitly contrast with alternatives like disassemble_hex or analyze_code_flow. No when-to-use or when-not-to-use guidance.

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