get_rule

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

With no annotations provided, the description carries the full burden. 'Get a single rule' accurately conveys a read-only, single-resource operation, which is the core behavioral trait, but it does not disclose error behavior, authorization needs, or whether related data is expanded.

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 six words, front-loaded with the action verb, and contains no filler. For a single-parameter getter, this length is appropriate.

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 enough that a long description is unnecessary, but with no annotations, no output schema, and no reference to sibling retrieval tools, an agent is left without guidance on failure modes or how this differs from list_rules.

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 0%, so the description needed to clarify the 'id' parameter. It does not: 'id' is only inferable as the rule identifier from the tool name, with no format, source, or example provided.

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 ('Get') and resource ('a single rule'), clearly identifying this as a retrieval operation. The singular 'rule' distinguishes it from list_rules, though it does not explicitly say the rule is fetched by its unique ID.

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 given about when to use this tool instead of list_rules or get_rule_group, and there is no mention of preconditions such as needing a known rule ID. The usage context is left entirely to inference.

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