gangtise_income_statement

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

No annotations are present, and the description does not disclose behavioral traits such as data availability, error handling, rate limits, or any side effects beyond a basic query. The agent receives no insight into reliability or constraints.

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 short and to the point, with only two sentences. The date context note is boilerplate but does not detract greatly. However, it could be structured to highlight key differentiators more effectively.

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 tool has 7 parameters and no output schema, the description is minimal. It does not explain return format, pagination, handling of multiple periods, or how to interpret cumulative data. The presence of many closely related siblings increases the need for context, which is missing.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the already detailed parameter descriptions in the schema. It merely restates that filtering is supported, which is obvious.

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 it queries A-share income statements on a cumulative basis, and mentions supported filters. However, it does not explicitly distinguish from siblings like gangtise_income_statement_hk or gangtise_income_statement_quarterly, which are very similar in name and purpose.

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 is provided on when to use this tool versus alternatives. For example, it does not specify that this tool is for A-share stocks only, nor does it suggest siblings for other markets or reporting types.

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