gangtise_balance_sheet

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

No annotations exist; description only mentions filtering capabilities. It does not disclose read-only nature, authentication needs, rate limits, or output format, leaving behavioral traits ambiguous.

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?

Description is one sentence with a relevant, albeit meta, date context prefix. It is concise but could separate tool behavior from system instructions.

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?

No output schema provided, and description does not explain return values. For a data retrieval tool with 7 parameters, this is a significant gap in completeness.

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% with detailed descriptions. The description adds no extra meaning beyond schema, e.g., parameter dependencies or defaults. Baseline 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?

Description explicitly states it queries A-share balance sheet and supports filtering by period, fiscal year, and report type. The sibling tool 'gangtise_balance_sheet_hk' confirms distinction by market, making purpose specific and clear.

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?

Description implicitly limits usage to A-share balance sheets but does not explicitly state when to use vs alternatives (e.g., HK, US). No when-not-to or prerequisite guidance is provided.

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