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

Annotations already mark this as non-read-only and non-idempotent; the description adds the valuable behavioral detail that it returns 202 Accepted immediately and does the work asynchronously. This tells the agent not to expect a synchronous payload. It doesn't contradict any annotation.

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 tight sentence with the action front-loaded and the async behavior in a short second clause. No filler or repetition.

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 an async one-parameter action with annotations and a fully documented schema, the description covers the key invocation behavior (accepted immediately, background processing). It could improve by pointing to getClarityPortfolioIntelligence for later retrieval, but the sibling name makes that inferable, so the gap is minor.

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 only parameter, team_id, has a full schema description covering UUID format, the API-key vs OAuth behavior, and fallback semantics. With 100% schema coverage, the description does not need to add parameter details, so the baseline 3 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?

The description uses a specific verb ('Generate') with a distinct resource ('portfolio intelligence') and a clear source scope ('from all completed clarity processes'). This separates it from sibling retrieval tool getClarityPortfolioIntelligence and from generateClarityProcessLandscape/Snapshot.

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 indicates when it is relevant (intelligence over completed clarity processes) and sets expectations for an async fire-and-forget call (202, background processing). However, it does not explicitly contrast with getClarityPortfolioIntelligence for retrieving results or state when not to call it, so the guidance is implied rather than explicit.

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