reits_realtime_em

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds that the return type is a pandas DataFrame and the data source URL, which is minor but not contradictory. No information about data delays, pagination, or limits is provided.

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 but the first line repeats the annotation title exactly, adding no new information. The URL and return type are useful, so it is not overly bloated, but the redundancy slightly reduces 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?

For a simple, parameterless, read-only tool with good annotations, the description provides the scope (Shanghai/Shenzhen), source (Eastmoney), and return type (DataFrame). It is sufficiently complete for basic usage, though it could mention the sibling historical tools.

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 tool accepts zero parameters and the schema has 100% coverage, so the description need not explain parameters. Baseline 4 applies for parameterless tools.

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 explicitly states it returns 沪深 REITs-实时行情 (Shanghai/Shenzhen REITs real-time quotes), giving a clear verb and scope. It implicitly differentiates from historical REITs tools like reits_hist_em by specifying '实时行情', though it doesn't name them.

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 such as reits_hist_em or reits_hist_min_em. The description lacks any context about typical use cases, exclusions, or recommended alternatives.

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