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

With no annotations, the description carries the behavioral burden. It conveys a read operation and notes that the house rules are 'versioned', but it does not specify how versions are resolved, whether any side effects exist beyond implied read-only use, or what the response shape will be. The read intent is clear, but deeper behavioral context is absent.

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 two short sentences with no waste. It front-loads the resource and contents, then ends with a crisp usage directive. The enumeration of covered topics adds useful domain context rather than 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?

For a zero-parameter, low-complexity read tool, this is nearly complete: it names the resource, states what it covers, and tells agents when to read it. The only notable gap is that 'versioned' leaves ambiguous whether the response returns the current version or historical versions, but that is minor given the tool's simplicity.

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?

The input schema has no parameters, so there is no parameter-semantics burden for the description. Per the zero-parameter baseline, a 4 is appropriate; no additional parameter details are needed.

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 clearly identifies a specific resource ('the house rules'), enumerates its contents ('payment flow, prices, limits, visibility and the welcome'), and gives an explicit directive ('Read this before anything else') that conveys the read action. This distinguishes it from transactional or social sibling tools such as mint_invoice or post_thread.

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?

It provides clear temporal context: this tool should be used before anything else, positioning it as a prerequisite step. It does not name alternatives or exclusions, but none are obvious for a simple terms-access tool, so the guidance is adequate.

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