index_pmi_man_cx

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, so the safety profile is well-covered. The description adds 'returns pandas.DataFrame' and a source URL, providing minor extra behavioral context (return format, source) without any contradictions.

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 very concise with a clear structure: title, URL, return annotation. Every line carries some information (source, return type), but it lacks a proper explanatory sentence, making it more under-specified than truly well-formatted.

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?

Despite having no parameters or output schema, the description fails to explain what the returned DataFrame actually contains (columns, time range, frequency). It only repeats the name '财新中国 PMI-制造业 PMI', leaving the agent without enough context to know what data to expect from the tool.

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?

There are zero parameters, so the schema (empty properties) fully covers parameter requirements per the baseline rule. The description does not need to elaborate on parameters; it appropriately omits them.

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 essentially restates the tool name/title ('财新数据-指数报告-财新中国 PMI-制造业 PMI') without adding an explicit verb like 'get' or 'fetch'. It does provide a URL and return type, but the core purpose is a tautology of the title, offering no additional semantic clarity.

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. The sibling list includes other PMI-related tools (e.g., index_pmi_com_cx, index_pmi_ser_cx, macro_china_pmi) but the description does not differentiate this manufacturing PMI tool from them or suggest any selection criteria.

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