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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real context beyond that: it takes no input and it returns tagline, the file's url, and rules objects with rule/title/part, plus routes single-rule lookups to describe_rule. Minor gap only in not stating anything about pagination or caching of the source file.

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?

Dense but front-loaded: purpose first, then usage trigger, then alternatives, then return shape. Every sentence carries information, though the middle clauses are somewhat packed and could be split for readability.

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 zero-input, read-only list tool with an output schema, the description covers purpose, usage trigger, alternatives, and return shape. Nothing an agent needs to select or invoke it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description still explicitly states 'No input,' confirming the empty schema rather than leaving it implicit.

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 resource (the vocabulary's conventions/R-rules from CONVENTIONS.md) and its scope (R0 onwards), and explicitly distinguishes itself from sibling behavior by noting that company-specific rules are entities handled by list_entities/get_entity. An agent can tell it apart from list_entities and describe_rule without opening schemas.

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?

Gives an explicit trigger ('Use to resolve a number a schema or refusal cites, such as R9') and names the alternatives for the adjacent case (company rules → list_entities and get_entity). The condition selecting this tool versus its siblings is unambiguous.

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