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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: amounts are in cents, names are member-typed, the tool resolves rates across five possible sources, and it is gated behind Pro. That is meaningful operational detail an agent cannot infer from the annotations.

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?

It is a single sentence with no filler, but it is a dense run-on with stacked parentheticals that interrupts the core claim before reaching the important 'amounts in cents / Pro feature' facts. The key qualifications trail the long middle clause rather than being front-loaded.

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?

There is no output schema, so the description carries the burden of describing return values — and it does, enumerating project rate, client rate, per-person rate, the effective new-hour rate, and its provenance. Missing only pagination/response-shape details and per-person error behavior for non-owners.

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 coverage is 100% with a single required parameter already documented as 'The project.' The description's phrasing 'For a project' aligns with boardId but adds no new syntax or format detail beyond the schema, so the 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?

The description clearly states the resource — per-person billing rates within a single project — including the precedence chain (member, project, client, team, none) that distinguishes it from a flat rate listing. It reads as a noun-phrase fragment rather than a verb+resource statement, so the action ('get') is only implied, but an agent can tell this apart from set_member_rate or list_team_rates without opening the schema.

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?

'For a project the user owns' gives a useful precondition (ownership scope) and 'A Pro feature' warns of an entitlement gate. However, it never names competing siblings such as list_team_rates or get_profitability_report, nor says when to prefer this over them, so usage is only implied.

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