online_value_artist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type but discloses nothing about network behavior, latency, pagination, or data limitations. It is a minimal addition beyond 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 description is extremely brief, containing a title, a URL, and return type information. It is not verbose, but it reads as a docstring fragment rather than a well-structured description. The lack of a proper sentence structure makes it slightly less accessible.

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 must explain the returned data. It only says it returns 'artist traffic value' as a DataFrame, leaving column names, row semantics, and data granularity unspecified. For a simple tool this could be acceptable, but the ambiguity makes it incomplete for an agent that must interpret the output.

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 input schema is empty and the baseline is 4. The description correctly focuses on the return value, which is the only meaningful semantic here. No additional parameter information is needed.

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 states the tool returns artist traffic value from endata.com.cn, and specifies the return type as pandas.DataFrame. This is a specific verb+resource pairing, though it does not explicitly differentiate from sibling tools like business_value_artist, which might overlap in domain.

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 about when to use this tool versus alternatives. It is a zero-parameter function with no context on use cases, prerequisites, or complementary tools. The only implied usage is 'call it to get artist traffic value'.

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