stock_zdhtmx_em

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds a source URL and a pandas.DataFrame return type, but omits data freshness, pagination, scope, and the meaning of the confusing ':return: 股东大会' line.

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 docstring is short and front-loads the source/resource name before the URL and parameter fields. It has no major filler, but the questionable ':return: 股东大会' line slightly hurts clarity.

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?

Annotations cover the safety profile and the description gives parameter examples, but with no output schema it does not explain the returned columns, and it omits usage context. It is minimally adequate for a simple date-range data pull but leaves clear gaps.

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 0%, so the description carries the burden. It documents both parameters with Chinese labels and concrete YYYYMMDD examples, adding format and meaning beyond the schema, though it could specify inclusive/exclusive date behavior.

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?

Identifies the resource as 东方财富网 data center 重大合同明细 and provides a source URL. The resource is specific enough for an agent to recognize what data it fetches, though it lacks an explicit verb and does not differentiate itself from sibling stock-data tools.

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?

Only documents start_date and end_date; there is no when-to-use, prerequisite, or alternative-tool guidance. An agent gets no routing help among the many sibling stock/macro data tools.

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