getIncomeStatementTTM

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds context about 'real-time' data and coverage across company types, which supplements annotations without contradiction. It does not disclose potential issues like missing symbols or rate limits, but the annotations cover the safety profile.

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 sentences, front-loading the core purpose and use cases. It is concise without wasted words, though it could be more precise by mentioning 'TTM' or the data frequency.

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?

The tool has 2 parameters and no output schema. The description explains the purpose and use cases but does not describe the return structure or data fields in the income statement. This is adequate given the simplicity but leaves the agent guessing about the response format.

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 describes both parameters (symbol, limit) with clear descriptions, achieving 100% schema description coverage. The description adds no additional parameter meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 tool accesses real-time income statement data for public companies, private companies, and ETFs, with specific verbs like 'access' and 'track'. However, it does not differentiate from siblings like 'getIncomeStatement' or mention 'TTM' (trailing twelve months) in the description, which would help distinguish it.

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 usage for tracking profitability and trends but provides no explicit guidance on when to use this tool versus alternatives like 'getIncomeStatement' or 'getIncomeStatementGrowth'. With many sibling tools, more explicit direction would improve the score.

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