sc_holdings

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

With no annotations, the description carries the full burden, but it only states that data is live and includes prices, quantities, and market values. It does not disclose authentication needs, rate limits, error behavior, pagination, or how optional parameters affect the response.

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 two tight sentences with the core action and payload front-loaded. Every clause earns its place, and there is no redundant filler.

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?

Although an output schema exists, the description omits critical context for two optional parameters and gives no usage guidance versus sibling tools. For a broker data tool with no annotations, this is too thin to fully support correct invocation.

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 adds no meaning for include_ytd or portfolio_id. Both parameters are left entirely undocumented, so an agent cannot infer what values to provide or what effect they have.

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 uses a specific verb and resource: 'Get Scalable Capital portfolio holdings' and clarifies the payload with 'all positions with current prices, quantities, and market values.' It is clear enough to distinguish from siblings like sc_transactions or sc_quote, though it does not explicitly name those alternatives.

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 should be used when portfolio position data is needed, especially with 'Live broker data' signaling current values. However, it does not provide explicit guidance about when to choose this over sc_overview, sc_analytics, or sc_quote, nor does it mention any exclusions.

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