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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description does add that the result is account-scoped and is a single aggregate (total proposal count) rather than a collection, but it omits any auth/permission context and gives no indication of response shape beyond that one number.

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 short sentence plus the endpoint path; the key fact (total number of proposals) is front-loaded and there is no filler. Slight redundancy with the title and the raw endpoint reference cost it the top score.

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 zero-parameter, read-only aggregate endpoint with no output schema, the description supplies everything needed to call it correctly: what it returns, that it is account-scoped, and the underlying operation. Nothing material is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline for a no-parameter tool 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?

Names the specific resource (proposal statistics) and clarifies exactly which statistic is returned — the total number of proposals — which cleanly separates it from list_proposals. It is a noun phrase rather than a verb+resource statement, and it never explicitly contrasts itself with the sibling list tools, so it stops 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: an agent can infer it should call this when it needs a count rather than a full proposal list, but the description never says when to use this over bidsketch_list_proposals or bidsketch_list_client_proposals, nor does it state any preconditions. No explicit alternatives or exclusions are given.

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