Get XRC failure stats

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

The description notes 'read-only,' but with no annotations, it fails to disclose additional behavioral traits such as data aggregation scope, authentication needs, or rate limits. The burden of transparency is not met.

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, very concise and front-loaded. However, it sacrifices necessary detail for brevity, making it only adequate in structure.

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 complexity of 7 optional parameters and no output schema or annotations, the description is incomplete. It does not explain usage patterns or parameter dependencies for different XRC types.

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 input schema has 7 parameters with 0% description coverage, and the description adds no meaning to any parameter. The agent cannot infer the role or format of address, type, ostcId, etc.

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 clearly states it returns 'read-only invalid/failure statistics' for XRC-137 rules or XRC-729 OSTC/process filters, specifying the resource and verb. However, it does not differentiate from sibling tools like get_xrc_usage or get_xrc729_ostc_state, which may also return statistics.

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. The description lacks any mention of context, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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