GetSplits

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

With no annotations, the description carries full burden but provides minimal behavioral context. It mentions 'last 10+ years' which hints at data availability, but doesn't cover rate limits, authentication needs (apikey param exists), error conditions, or response format. The agent must infer behavior from parameters alone.

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?

Single sentence is appropriately concise and front-loaded with core purpose. However, it could be more structured by separating scope details from the main action.

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?

For a tool with 1 parameter (though nested object has 12 properties), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'split factor' is, how results are formatted, or important constraints like the 'Grow' plan requirement mentioned in the schema.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'split factor' means, how date ranges work, or the relationship between symbol/figi/isin parameters. The agent must rely entirely on schema property descriptions.

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 clearly states the action ('Returns') and resource ('date and split factor of shares'), specifying a time scope ('last 10+ years'). It distinguishes from siblings like GetDividends or GetPrice by focusing on stock splits, but doesn't explicitly contrast with similar tools.

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 GetDividends for dividend data or GetTimeSeries for price history. The description mentions 'Available starting from the `Grow` plan' in the schema, but this isn't in the main description text for usage context.

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