get_xrefs_to_class

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

With no annotations, the description carries the full burden of disclosing behavior. It only states 'find all references' without explaining pagination (offset, count), whether it is read-only, or what the output format is. Since an output schema exists but is not described, the agent may not understand the return structure.

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 sentence with no extraneous information. It is front-loaded and efficient, fulfilling the requirement of being concise.

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 the tool's three parameters and the presence of sibling tools, the description is insufficient. It lacks usage guidelines, parameter semantics, and behavioral details, leaving gaps that the structured fields do not fill.

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 coverage is 0% and the description does not elaborate on any parameters. 'class_name' is inferred from the tool name, but 'offset' and 'count' are unexplained, leaving the agent unaware of their roles in pagination.

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 'Find all references to a class' uses a specific verb and resource, clearly stating the tool's function. It distinguishes itself from sibling tools like 'get_xrefs_to_field' and 'get_xrefs_to_method' by specifying the target as a class.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_methods_of_class' or 'get_fields_of_class'. The description does not mention prerequisites, context, or exclusions.

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