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

readOnlyHint=true already establishes the safety profile, so the description's added value is return shape: it discloses that each line carries type, totals and an optional flag, which matters because there is no output schema. It does not mention pagination behavior or ordering, but the schema covers paging.

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?

One compact sentence front-loads the resource and its contents, followed by the endpoint. The endpoint reference is low value for an agent but costs little; nothing is wasted or buried.

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 read-only list tool with full schema coverage and no output schema, the description supplies the key missing piece (what each fee line contains). Ordering and pagination semantics are the only notable omissions.

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% and the single required proposal_id plus paging params are fully documented in the schema. The description's 'one proposal' reinforces the required id but adds no format or constraint detail beyond what the schema provides, 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?

States a specific verb (List) plus resource (fee lines) scoped to one proposal, and names the returned attributes (type, totals, optional flag). This clearly separates it from siblings like bidsketch_list_fees (global fee list) and bidsketch_get_proposal_fee (single fee).

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?

The scope 'one proposal' implies when to use it, but there is no explicit guidance on when to prefer bidsketch_list_fees, bidsketch_get_proposal_fee, or bidsketch_get_proposal_content. Usage is inferable but not stated.

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