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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds non-obvious behavioral context beyond that: the referenced members are included only "where available," warning the agent that the payload is conditionally populated. Remaining gaps (pagination, ordering) are modest but present.

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?

Two sentences, zero filler. The scope and output caveat come first, and the routing instruction follows, so the agent gets the identifying information before the procedural hint.

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?

Both parameters are optional and fully documented in schema, annotations cover the safety profile, and no output schema exists — so the description only needs to convey what comes back, which it does at a high level (rules plus referenced members). It stops short of saying whether the list is scoped to one application's full rule set or paginated.

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 100% and both parameters document their own defaults and cross-references (list_connections). The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("Lists the business rules of an application") and clarifies the underlying object type as "rule job definitions." An agent can identify the operation, though the parenthetical leaves some ambiguity versus the sibling list_job_definitions, which is not addressed.

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?

Explicitly names the downstream action: "Use it to find the exact rule name before run_business_rule." This gives clear workflow context and implicitly excludes the tool from execution tasks. No explicit when-not conditions or alternative discovery tools are offered, keeping it short of a 5.

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