fahali_get_portfolio_risk

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

Describes the return structure (overall risk score, VaR, drawdown, per-position breakdown) and implies read-only nature. Without annotations, the description adequately discloses the tool's behavior.

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 concise sentences, front-loaded with purpose and outputs, followed by requirements. No extraneous 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?

Covers purpose, outputs, and prerequisites. Given no output schema, it explains return values adequately. Might be enhanced with data freshness details, but not essential.

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?

No parameters exist, so baseline of 4 applies. Description does not need to add parameter meaning.

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?

Clearly states the tool retrieves portfolio risk assessment and lists specific outputs (risk score, VaR, drawdown, per-position breakdown). Distinct from sibling tools which address capital flow, contagion, and market verdict.

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?

Specifies prerequisites (connected exchange accounts, Elite tier or higher) indicating when the tool is usable. Implicitly guides against use without those conditions, but does not explicitly contrast with siblings.

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