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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful data-scope context by noting only public documents and no private owner information, but it does not discuss error behavior, what 'current' means, or return characteristics.

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?

Two short, front-loaded sentences with no filler. The scoping constraints are stated immediately and every phrase contributes to the tool's purpose.

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 simple one-parameter read tool with rich annotations, the description gives adequate basic context about public scope and documents. However, it omits any explanation of the required identifier and, with no output schema, does not describe what is returned beyond 'public documents'.

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 should compensate by explaining the sole required parameter 'projectPublicId'. Instead, it says nothing about the identifier, its UUID format, or that it refers to a project public ID, leaving the schema to carry all parameter meaning.

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?

The description uses a specific verb+resource ('Read a current public opportunity and its public documents') and scopes it to public/current data. It is clearly distinct from write-oriented siblings like create_project_draft, though it does not explicitly differentiate itself from list_opportunities or evaluate_opportunity.

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 description implies when to use it by specifying 'current public opportunity' and excluding private owner information, but it never explicitly names alternatives or states when not to use it versus list_opportunities or evaluate_opportunity.

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