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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real context beyond that: it enumerates exactly what data the response contains and confirms parity with the underlying REST endpoint, which reassures an agent about fidelity. It stops short of noting auth or rate limits, but for a static rule lookup that is minor.

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?

Front-loaded with the core payload description, then the REST equivalence. The parenthetical field list is dense but every item is informative about the return contents. No filler sentences.

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?

With no output schema, the description usefully compensates by listing the returned fields, and the REST mapping gives a precise mental model of the call. A one-parameter read tool with full annotation coverage is adequately served; only the absence of sibling routing guidance keeps it from a 5.

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 single parameter is an enum with an inline hint ('Program id from list_firms'), so the schema does the heavy lifting. The description adds no parameter-level detail beyond restating the program selector in the REST URL form, so baseline 3 applies.

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 verb (get) and resource (rules) scoped to one program, and enumerates the payload contents (daily-loss, max-drawdown, static/trailing mode, lock, reset time, notes, source links, copy-trading policy). The REST endpoint mapping (GET /api/v1/rules?program=<id>) pins the semantics exactly. Clearly distinguishable from check_drawdown and list_firms.

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?

Usage is implied rather than stated: it is a read for a single program's rule set, and the schema note 'Program id from list_firms' hints at the workflow. However, it never says when to prefer this over check_drawdown or when list_firms should be called first, and offers no exclusions.

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