futures_contract_detail

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds that the return is a pandas DataFrame and shows a Sina URL, offering source context, but it does not disclose additional behavior such as output columns or rate limits.

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 brief and front-loaded with the main purpose. The embedded docstring and URL slightly reduce clarity, but the overall structure is acceptable for a tool with one parameter.

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?

With no output schema, the description should ideally describe return fields, but it only states the return is a 'pandas.DataFrame' of futures contract details. The example URL adds some context, yet the actual columns and data content remain unspecified, leaving a meaningful gap.

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 schema provides no description for 'symbol' (0% coverage). The description calls it '合约' (contract) and includes an example URL with 'V2101', but it does not explain expected formats like the default 'AP2101' or exchange-specific prefixes, providing only minimal compensation for the missing schema documentation.

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 '查询期货合约详情' (query futures contract details), providing a specific verb and resource. However, it does not differentiate from the similarly named sibling tool 'futures_contract_detail_em', so it lacks explicit sibling distinction.

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 like futures_contract_detail_em or futures_contract_info_*. The Sina URL hints at a data source, but this is not stated as a selection criterion.

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