stock_js_weibo_report

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the return type (pandas.DataFrame) and the data source URL, but doesn't disclose any additional side effects or edge cases. It does not contradict the annotations.

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 compact, containing only the title, source URL, parameter help, and return type. Each element serves a purpose, though the structure is somewhat docstring-style rather than natural language, it remains efficient and front-loaded.

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 single-parameter read-only report fetcher with no output schema, the description covers the key aspects: what it returns, the parameter options, and the source. It doesn't list the columns or content of the report, but given the low complexity and strong annotations, it is sufficiently complete.

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 a `time_period` string with a default but no description. The description compensates by enumerating the valid enum values and their human-readable labels (e.g., CNHOUR12 means 12 hours), which is essential for correct usage. This goes beyond the schema's bare type and default.

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 identifies the resource as a Weibo sentiment report from the Jin10 data center, with a parameterized time period, and the return statement confirms it returns the report. This distinguishes it from sibling `stock_js_weibo_nlp_time` by being a report rather than NLP time-series data, though it lacks an explicit verb like 'fetch' or 'query'.

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?

There is no guidance on when to use this tool versus alternatives. The only usage context is the time_period parameter dictionary, which implies the caller chooses a period, but no exclusions or comparisons to similar tools such as `stock_js_weibo_nlp_time` are provided.

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