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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the returned fields (status, budget, proposal count), but says nothing about result ordering or that the list is paginated via cursor.

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 fragment with no filler, and the scope qualifier ('as a buyer') is front-loaded ahead of the returned fields. Slightly abbreviated to the point of omitting the action verb, but nothing is wasted.

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 paginated read-only listing there is no output schema, so the description's mention of status/budget/proposal count is genuinely useful. However, it omits that results are paged and how to continue, leaving an agent to discover cursor semantics from the schema alone.

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 all three parameters (query, cursor, status) are documented with enums enumerated, so the description adds nothing beyond the schema. Baseline 3 applies when the schema carries the full burden.

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 resource (projects) and narrows it precisely to 'this account posted as a buyer', which separates it from search_projects and list_watchlist. The verb is only implied by the tool name rather than stated in the description, so it stops short of a full verb+resource statement.

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 'this account posted as a buyer' qualifier implies when this tool applies, but no sibling is named and no exclusion is stated (e.g. 'to search other buyers' projects, use search_projects'). Usage is inferable rather than explicit.

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