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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It contributes the ordering ("newest first") and implies a bounded result set via "recent", but leaves the cap, pagination behavior, and whether statuses are included undefined — notable gaps for a listing tool.

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 front-loaded sentence with no filler, and ordering is stated up front where it matters. It is efficient, though the brevity comes at the cost of the parameter and scope detail noted elsewhere.

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 and an undocumented enum parameter, the definition should say more: whether status filters results, what "recent" bounds, and what the response shape is. As written, an agent cannot tell how to use the status filter or how many items to expect.

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 0%, so the description carries the full burden, yet it never mentions the optional status parameter or the meaning of its pending/approved/rejected enum values. It only indirectly conveys that project_id is required ("for a project"), leaving half the parameters underexplained.

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 and resource ("Lists recent proposals") plus scope ("for a project") and ordering ("newest first"). It does not explicitly contrast with get_proposal or list_projects, but the resource noun is distinct enough that an agent can differentiate without opening a 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?

Usage is only implied: an agent can infer this is for enumerating proposals within a known project. There is no guidance on when to prefer get_proposal for a single record, nor any exclusion or prerequisite (e.g., auth or project access requirements).

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