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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes well beyond that: budget.read gating that excludes unreadable projects from the rollup, the budgetHiddenCount field explaining the omission, the GREY RAG rule for plans with no tasks, and the contents of the attention block. That is substantial behavioral context the annotations do not carry.

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?

Front-loaded with what is aggregated, then the permission caveats and the sibling routing, all in dense sentences with no filler. It is somewhat long, but each sentence (budget gating, RAG rules, attention contents, permissions, alternative) earns its place.

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?

No output schema exists, yet the description effectively documents the return shape (metrics, budgetHiddenCount, plans with RAG/url, attention rows with url) plus the permission envelope. An agent has everything needed to call it and interpret the response.

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 0% and the description gives no syntax or format for portfolioId, only implying the single-portfolio scope. With one self-evident identifier parameter, this is the expected baseline but the description adds nothing new for the 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+resource (aggregate metrics for one portfolio) and enumerates the exact content: project count, task totals, status breakdown, RAG distribution, currency-normalized budget rollup. It is clearly distinguishable from the sibling get_portfolio, which it names for per-project detail.

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?

Explicitly routes the agent: 'For per-project detail use get_portfolio.' It also states the prerequisites for invoking it (BUSINESS+ portfolios feature, org.portfolio.manage, MANAGER+ default, budget.read for the rollup), so the agent knows both when to call it and whether it can.

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