bili_user_dynamics

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

With no annotations, the description must carry behavioral disclosure. It indicates read-only behavior ("No posting/following") and notes the cursor is a native string, but it omits permissions, rate limits, and pagination behavior, leaving meaningful gaps for a tool with no annotation coverage.

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 two short, front-loaded sentences with no filler. It is efficient, though its terseness contributes to gaps in parameter and usage explanation.

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?

An output schema exists, so return values need not be described. However, for a tool with three undocumented parameters and no annotations, the description omits what uid and num control and does not clarify the difference from sibling user-content tools, leaving an agent under-informed.

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?

Schema description coverage is 0%, so all three parameters lack structured documentation. The description only adds meaning for the cursor ("native string cursor"), while the required uid and optional num remain unexplained, which is insufficient compensation.

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 a specific verb and resource ("Read public user dynamics") and distinguishes itself from sibling write actions with "No posting/following." It is somewhat ambiguous about what "dynamics" means versus bili_user_videos or bili_user_info, but the core purpose is clear.

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?

The phrase "No posting/following" provides a negative exclusion, implying this is for reading rather than writing. However, it does not explicitly say when to use this tool over siblings like bili_user_videos or bili_user_info, leaving usage selection largely inferred.

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