lock_business_ruleset_revision

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

With no annotations, the description carries the full burden. It discloses a critical behavior: the revision-creation request replaces full content from the body, and omitting rules would wipe the live rule set's rules. This goes beyond the basic 'lock' semantics and warns of a dangerous side effect.

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 three paragraphs, each serving a distinct purpose: main action, contextual usage, and a critical caveat. It is front-loaded with the primary purpose and stays focused, though the third paragraph is slightly dense. No filler.

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 (immutable revision, full-content replacement) and the presence of an output schema, the description adequately covers the workflow and pitfalls. It explains the need to fetch rules with a specific media type and resend them, which is essential context for safe invocation.

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 are well-described in the schema (ruleset_id UUID vs name, revision_type defaults). The description adds context about integral+json fetching but doesn't meaningfully enhance parameter understanding, so 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?

The description opens with a specific verb+resource: 'Lock the current state of a rule set as an immutable revision.' It clearly distinguishes from the sibling tool lock_decision_flow_revision by focusing on rule sets, and further elaborates that revisions are immutable and referenced by decisions.

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 provides clear context: a revision must exist before wiring a rule set into a decision flow, and you must call again after editing rules. It doesn't name alternatives explicitly but explains the timing and prerequisites, which is strong guidance.

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