show_rule

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

No annotations are provided, so the description carries the burden of behavior disclosure. 'Show' communicates a non-mutating read operation, but it doesn't specify what fields count as 'detailed', what happens for an unknown key, or the output structure. Adequate for a trivial read, but not richly transparent.

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, repetition, or tangential information. For a one-parameter lookup tool, this is appropriately minimal.

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 simple one-parameter read operation with no output schema, the description is minimally sufficient: it indicates that a rule key is needed and that detailed rule information will be returned. However, it doesn't enumerate what 'detailed information' includes or address edge cases, so it stops short of being fully self-contained.

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 the only parameter, key, is already documented with an example format. The description adds no additional parameter semantics, but it doesn't need to because the schema fully explains what to provide.

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 concrete verb ('Show') and a specific resource ('a rule'), clearly identifying this as a single-rule read operation. It doesn't explicitly contrast with siblings like list_rule_repositories, but the singular focus on one rule's detailed information makes confusion unlikely.

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 usage is implied: call this when you need detailed information about a specific rule identified by its key. It does not state exclusions or name alternative tools, but the trigger condition is reasonably inferable from the description and parameter.

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