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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral detail about what data is aggregated (commitments from all life domains + promoted Playbooks) and how it is organized (grouped by urgency), which helps the agent set expectations without contradicting annotations.

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 sentences cover the core purpose and usage guidance with zero wasted words. The key scoping ('cross-domain', 'portfolio') is front-loaded, and the examples are concrete and immediately actionable.

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 only one optional parameter, full schema coverage, and annotations covering safety, the description provides everything an agent needs: what the tool returns, the level of aggregation, and when to invoke it. No output schema exists, but the description sufficiently describes the outcome without needing to enumerate exact fields.

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 100% for the single optional companyId parameter, so the schema already fully documents it. The description adds no parameter-specific information, making the baseline 3 appropriate.

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 states a specific verb ('Get') and resource ('executive landscape'), then elaborates with what it shows: 'commitments from all life domains + promoted Playbooks across the portfolio, grouped by urgency.' This clearly distinguishes it from siblings like list_commitments or get_playbook by emphasizing the cross-domain, portfolio-level scope.

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 gives explicit use cases: 'Use when the user asks "what should I focus on?", "what's on my plate?", "am I dropping anything?", or similar portfolio-level questions.' This is clear context, though it does not explicitly name alternative tools or state when not to use this one, so it stops short of a 5.

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