List Business Rules

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds rule-set scoping, but the phrase 'all rules' is slightly misleading given the limit parameter, and no extra behavioral context such as pagination or output shape is disclosed.

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 filler or redundant information. It is concise while still naming the verb, resource, and scope.

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?

For a read-only list operation with fully documented parameters and an output schema, the description is largely sufficient. The main gaps are the absence of explicit sibling-tool routing and the potentially misleading 'all rules' wording, but these are minor given the rich schema and annotations.

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?

Both limit and ruleset_id are fully described in the input schema with 100% coverage, so the description adds no parameter-level meaning beyond what the schema already provides. The 'all rules' wording does not clarify how limit interacts with the result set.

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 uses a specific verb ('List') and a clear resource ('all rules inside a SAS Business Rules rule set'), which distinguishes it from list_business_rulesets and rule-level CRUD tools. It is not a tautology and immediately conveys what the tool does.

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 you need rules within a specific rule set, but it does not explicitly contrast this tool with list_business_rulesets or get_business_rule. No when-not conditions or alternative routing are provided, leaving selection mostly to the tool name and schema note.

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