Find reusable XRC-137 rules

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

The description mentions 'read-only' which informs about non-destructiveness, but provides no details on authentication, rate limits, or behavior under various input conditions. With no annotations provided, the description carries full burden but falls short.

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, concise sentence that front-loads the purpose with no filler words. Every word adds value.

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 complexity (8 parameters, nested objects, no output schema), the description is too sparse. It omits parameter meanings, return format, pagination, and error handling, leaving agents underinformed.

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%, and the description does not explain any of the 8 parameters (owner, draftRule, ruleHash, etc.). It only hints at 'metadata-assisted search' but leaves agents guessing about required inputs beyond 'owner'.

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?

Description clearly states the tool is for searching existing owner XRC-137 contracts that could be reused, with a read-only metadata-assisted approach. It specifies the resource (XRC-137 contracts) and action (search for reusable ones), but does not explicitly differentiate from similar sibling like 'get_unused_xrc137_rules'.

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 description implies usage when searching for reusable contracts to avoid redeployment, but lacks explicit when-not-to-use guidance or comparisons with alternatives like 'get_unused_xrc137_rules' or 'read_xrc137_rule_json'.

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