Analyze Portfolio Context

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

Annotations already declare readOnlyHint=true and idempotentHint=true; the description aligns by stating 'Read-only' and further adds transparency by clarifying that the tool does not make allocation or deployment recommendations. This extra context is valuable beyond the 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?

The description is a single sentence, which is concise, but given the tool's complexity and 44 parameters, it is too brief. A more structured breakdown (e.g., bullet points for parameter categories) would improve readability without sacrificing conciseness.

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 44 parameters, no output schema, and zero parameter documentation, the description is grossly incomplete. It does not specify expected outputs, parameter dependencies, or how to interpret results. The tool's complexity demands a more thorough description.

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?

The input schema has 44 parameters with 0% description coverage. The tool description provides no explanation of any parameter, leaving the agent to infer meanings from field names and enums. For such a complex tool, the description must compensate, but it fails entirely.

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 explicitly states 'Read-only whole-account context analyzer' and lists specific components (account snapshot, stock factors, option factors, risk budgets, concentration context, warnings). It clearly distinguishes from siblings that perform order placement or recommendations by noting it does not provide allocation or deployment recommendations.

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 implies the tool is for obtaining portfolio context without recommendations, but it does not provide explicit guidance on when to use it versus other tools like saxo_get_balance, saxo_list_positions, or saxo_screen_stock_factors. The 'read-only' nature is clear, but alternatives are not mentioned.

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