calculate_position_size

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

No annotations are provided. The description mentions 'Paid Fintools MCP required', hinting at a subscription requirement, but does not disclose other behavioral aspects such as required permissions, side effects, or what happens with invalid inputs.

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 but fails to convey essential information. For a tool with 6 parameters and no schema descriptions, the description is under-specified, lacking necessary detail.

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 the complexity (6 parameters, 4 required, no schema descriptions) and the presence of an output schema (not detailed), the description is incomplete. It does not explain what the output represents or how to interpret results.

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 tool description does not elaborate on any parameter (e.g., what 'risk_pct' represents, defaults for optional parameters). The description adds no semantic value beyond the parameter names.

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 'risk-based position sizing', which indicates the tool calculates position size based on risk parameters. However, it lacks specificity on what exactly is computed (e.g., number of shares, dollar amount) and does not differentiate from the sibling tool 'calculate_atr_position' that likely calculates position size using ATR.

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 guidance on when to use this tool versus alternatives like 'calculate_atr_position'. No prerequisites or context for appropriate usage are provided.

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