list_business_rules

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

Annotations already provide readOnlyHint=true and openWorldHint=true, establishing it as a safe read operation. The description adds the useful prerequisite that SCRIPTING_ENABLED must be true, which is behavioral context beyond annotations. However, it does not disclose filtering behavior, pagination, or return format. Given annotation coverage, this is adequate but not rich.

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 that front-loads the core action and includes a critical prerequisite. It is concise and contains no filler or redundant information.

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?

The tool is simple with optional parameters and no output schema. The description covers the basic action and a prerequisite, but lacks usage guidance regarding alternatives or any mention of what the response contains. For a minimal list tool, it is minimally complete but leaves gaps in when-to-use context.

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 documents all three parameters (limit, table, active) with clear descriptions, giving 100% schema description coverage. The description adds no additional parameter semantics beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 the action 'List business rules', with a specific verb and resource. This distinguishes it from sibling tools like 'get_business_rule' (single rule) and the create/update variants. The purpose is immediately evident.

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 only mentions a prerequisite (SCRIPTING_ENABLED=true) but does not explain when to choose this over 'get_business_rule' or how it differs from 'list_script_includes' or other listing tools. There is no exclusion or alternative context.

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