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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds value by naming the returned fields (status values Pending/Viewed/Accepted/Declined and a draft flag) and the underlying endpoint. It says nothing about pagination behavior, ordering, or what happens for a client with no proposals, so it adds context without being rich.

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?

A single compact sentence with the scope restriction front-loaded, followed by the endpoint path. No filler, though the raw endpoint adds little for an agent that cannot call HTTP directly.

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 carries the burden of describing returns and does so only partially — it names status and draft flag but not the overall response shape (list vs. wrapper, pagination metadata). Annotations cover the read-only safety profile, so the remaining gap is moderate rather than critical.

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 all three parameters (client_id, page, per_page) are documented in the schema itself, including defaults and maximums. The description adds only the implicit note that client_id scopes the result and nothing about page/per_page, 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 (list) and resource (proposals) plus a clear scope restriction: proposals belonging to one client. It does not explicitly differentiate itself from the sibling bidsketch_list_proposals, which an agent could easily confuse it with, so it falls short of a 5.

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 only implied: the phrase 'of one client' suggests you should call this when you have a client_id rather than when you want the full proposal list. There is no explicit 'use this instead of bidsketch_list_proposals when...' guidance and no stated prerequisites besides the required id.

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