stock_financial_us_report_em

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the data source URL and return type (pandas DataFrame) but discloses no rate limits, pagination, or formatting nuances. This is acceptable for a read-only tool but contributes only modest behavioral context beyond the annotations.

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 follows a clear docstring format with a title, URL, parameter entries, and return type. It is reasonably concise without unnecessary fluff, though the :return: line duplicates the title. The structure makes the information easy to scan.

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 absence of an output schema, the description would benefit from explaining the DataFrame's structure, such as row content or key columns. It does provide the source URL, parameter semantics, and safety annotations, but lacks details on return value composition or edge cases. For a straightforward report retrieval tool, it is minimally complete.

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 has zero property descriptions, so the description compensates by explaining each parameter: stock (股票代码), symbol (choice of three statement types), and indicator (choice of annual/quarterly periods). It also lists the allowed values for symbol and indicator, which is valuable. It lacks further elaboration on value meanings or examples, but the provided labels are sufficient for domain-aware users.

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 identifies the tool as a source for US stock financial reports (三大报表) from East Money, supported by the URL and title. It distinguishes from siblings that cover A-share or HK financials by specifying '美股'. However, it lacks an explicit action verb like 'fetch' or 'get', though the intent is unambiguous.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, exclusions, or specific use cases. It simply lists parameters and return type, leaving tool selection reasoning entirely to the agent.

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