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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds genuinely useful semantics: the values are ESTIMATES derived from purchase price, purchase date, and the portfolio's lending assumptions, and are explicitly not loan records — a caveat an agent must know before presenting them as facts.

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, no padding: the content list comes first and the important estimate caveat is front-loaded immediately after. Every clause carries information.

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, the description need not enumerate return fields, yet it usefully summarizes them and flags the estimate-vs-record distinction. The only gap is the absence of routing guidance against the many sibling portfolio tools.

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?

Only one parameter, and the schema documents it fully (100% coverage) including its provenance ('From list_portfolios.'). The description adds nothing about the parameter, 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?

States the concrete content returned — estimated loan balances, LTV per aircraft, book summary, watchlist — which is a specific resource+verb and distinguishes it from generic siblings like get_portfolio_overview or get_portfolio_positions. It stops short of naming those siblings, so an agent must infer the routing.

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?

No when-to-use statement and no alternatives named, despite many portfolio-scoped siblings (get_portfolio_overview, get_portfolio_positions, get_portfolio_aircraft). The lender framing implies a lending-analysis context but the agent gets no explicit trigger condition.

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