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

The annotations already declare this is a read-only, idempotent, non-destructive, closed-world retrieval tool. The description adds useful context beyond annotations, including the 1-credit cost and that rules are quoted from firm pages with links and check dates.

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 compact and front-loads the credit cost, then covers scope, fields, provenance, and usage. The parenthetical list is dense but still readable and purposeful.

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 read-only lookup with two optional parameters and no output schema, the description provides enough context about coverage, rule types, provenance, cost, and intended use. The main gap is that the firm parameter's expected format and optional rule filtering behavior are not fully clarified.

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 50%, with the rule parameter having examples but the firm parameter undocumented. The description compensates somewhat by listing rule categories such as daily loss, max loss, and news rule, but it does not explain the expected firm identifier format or behavior when parameters are omitted.

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 states that this tool returns quoted rules from 32 prop trading firms, including specific rule categories and provenance details. It distinguishes itself from a ranking, but does not explicitly differentiate from the listed sibling tools.

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 gives a clear usage context: use when a bot must stay inside a prop challenge's limits, and explicitly says it is not a ranking. It does not provide explicit when-not scenarios or name alternative tools for related needs.

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