Get unused XRC-137 rules

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

The description declares it is read-only and lists rules with no observed usage, which are key behavioral traits. However, it fails to disclose ordering, exhaustiveness, error handling, or any performance implications. With no annotations, the description carries the burden but provides only basic transparency.

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, front-loaded sentence with no unnecessary words. It is maximally concise and well-structured for a simple tool.

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 no output schema, annotations, or parameter descriptions, the description should provide more context about return format, pagination, and behavior for missing or invalid owners. It completely lacks details on the 'limit' parameter and output structure, leaving significant gaps for proper use.

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 must explain parameters. It only implicitly references 'owner' in the phrase 'owner XRC-137 rules', and completely ignores the 'limit' parameter. No additional meaning is added beyond the schema's type and pattern.

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 is a read-only list of owner XRC-137 rules with no observed usage. It uses specific verb 'list' and resource 'unused rules', and while it implicitly distinguishes from related siblings like 'find_reusable_xrc137_rules', it does not explicitly differentiate.

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 like 'find_reusable_xrc137_rules' or 'read_xrc137_rule_json'. There is no mention of prerequisites or context for usage.

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