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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's burden is low. The description adds a small semantic detail, 'versus its target allocation,' but does not disclose any behavioral context such as whether a target allocation must already exist.

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?

The description is very short—one compact phrase with no filler. It is easy to read and likely appropriate for a simple getter, though the missing grammar makes it slightly more like a fragment than a clear sentence.

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?

Given output schema is present and annotations cover safety, a brief description is acceptable. However, the description does not address the closely related sibling get_drift_snapshot, nor fully explain parameter roles, so if an agent encounters both tools the definition is not fully adequate on its own.

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 0% and the description does not explain household_id or portfolio_id. The phrase 'portfolio versus its target allocation' implies portfolio_id identifies the portfolio being evaluated, but household_id isn't addressed, so the meaning must be inferred from parameter names alone.

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 the tool's resource and scope: drift of a portfolio versus its target allocation. This clearly communicates what the tool produces, though it lacks a verb and doesn't distinguish it from the closely named sibling get_drift_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 gives no guidance on when to use this tool instead of similar siblings like get_drift_snapshot or get_portfolio_positions. There is no mention of prerequisites, exclusions, or when-not-to-use, leaving the agent to infer selection from naming alone.

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