energy_carbon_domestic

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the source URL and return type (pandas.DataFrame), but does not elaborate on data content, rate limits, or other behavioral aspects. This adds some context but lacks depth.

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 concise, containing only essential information: title, source URL, parameter documentation, and return type. Although the structure is docstring-style and mixes Chinese/English, it is appropriately sized and every line contributes value.

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?

For a simple 1-parameter, read-only tool, the description is adequate but incomplete. It states the return type is a pandas.DataFrame but does not describe what columns or metrics are included in the returned '市场信息'. With no output schema, the description should provide more detail about the return value's structure.

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 only a default value with no description (0% coverage). The description compensates by listing the allowed enum values ('湖北', '上海', '北京', etc.) and specifying the type as str, which gives agents the necessary parameter semantics beyond the bare schema.

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 the tool retrieves market information ('行情信息') from a specific carbon trading website (tanjiaoyi.com). It identifies the resource and action, but it does not explicitly differentiate from sibling tools like energy_carbon_bj or energy_carbon_gz, which serve similar regional purposes.

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 its alternatives. The description merely documents the parameter and return type, with no mention of use cases, exclusions, or when region-specific siblings might be preferable.

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