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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds real behavioral value beyond them by disclosing the "available is false when no profile exists yet" edge case, which an agent needs to handle a null/empty profile.

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, front-loaded with the substantive content of the profile and closing with the availability caveat. No filler; only minor tightening possible.

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?

An output schema exists, so return-value documentation is not required, yet the description still orients the agent on what the profile contains and the empty-profile case. For a one-parameter read tool this is sufficient, lacking only sibling differentiation.

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?

There is a single parameter with 100% schema coverage, and the schema description already tells the caller where line_id comes from (list_portfolio_aircraft). The description adds nothing about the parameter, so the baseline 3 for fully documented schemas 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 names a specific resource (one portfolio aircraft) and enumerates the profile's contents — weekly flying days vs. seasonal expectation, local/pattern vs. cross-country mix, detected utilisation changes. That is more concrete than a tautology, but it never distinguishes itself from near-neighbours like analyze_flight_usage or assess_flight_activity_risk, so it falls short of a 5.

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?

"One portfolio aircraft" implies the line_id scope and the parenthetical in the schema points to list_portfolio_aircraft, and the availability caveat gives some context. However, there is no explicit when-to-use vs. when-not guidance, and no routing away from the similar read tools in the sibling list.

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