gangtise_earning_forecast

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

No annotations are provided, so the description must disclose behavioral traits. It only states the query function and a date conversion rule, failing to mention important aspects like read-only nature, required permissions, rate limits, or the structure of the response. The description adds minimal behavioral context beyond the parameter schema.

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 lines: the first sets date context, the second defines the purpose. It is concise, front-loaded, and contains no redundant or irrelevant information. Every sentence serves a clear function.

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 4 parameters (including an array type) and no output schema, the description lacks details on the return format, how to use the consensusList array (e.g., selecting multiple metrics), and pagination or limitations. It adequately covers the date interpretation context but is incomplete for an agent to fully understand usage without additional inference.

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 100%, so the baseline is 3. The description's mention of EPS, PE, etc. aligns with the consensusList options described in the schema, but does not add significant new meaning. The date conversion rule is already present in the schema descriptions for startDate and endDate. Overall, the description adds marginal value beyond the schema.

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 it queries earnings forecast consensus expectations, listing specific metrics (EPS, PE, net profit, ROE). This clearly distinguishes it from sibling tools like gangtise_income_statement or gangtise_balance_sheet, which serve different financial data purposes.

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 includes a date interpretation note but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The usage is implied by the purpose, but no direct comparative guidance is given.

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