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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description usefully discloses that related entities (Pillar, Capabilities, Initiatives, Gate Decisions) are included, but says nothing about not-found behavior, permissions, or how deeply relations are expanded.

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; the core action comes first and the included fields follow as a compact enumeration.

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 an output schema present, rich annotations, and a fully documented single parameter, the description needs only to convey scope and included relations, which it does. Minor gap: no guidance on the not-found case or on obtaining the opportunityId beforehand.

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 the single opportunityId parameter already carries a format/pattern and description, so the description adds nothing about it. Baseline 3 applies when the schema does all the work and there is only one straightforward identifier parameter.

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 ('Fetches') and a precisely scoped resource ('one Strategic Opportunity'), and enumerates the payload (thesis, status, gate state, parent Strategic Pillar, linked Capabilities/Initiatives/Gate Decisions). The word 'one' cleanly separates it from the sibling opportunity_search, so an agent can pick it without opening the 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 the tool for retrieving a single known opportunity by ID rather than listing results. There is no explicit when-to-use vs. when-not statement and no mention that opportunity_search should be used first to discover the ID, which is the natural prerequisite.

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