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

No annotations are provided, so this description is the sole behavioral disclosure. It indicates a read-only listing action, but it does not describe output structure, ordering, or possible limitations. For a simple list tool, this is adequate but not deeply transparent.

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 a single, front-loaded sentence that directly states the action, resource, and output. It is free of filler words and extremely efficient.

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?

The tool is simple with no parameters, annotations, or output schema. The description clearly captures the purpose and output. However, it lacks any usage context or differentiation from siblings, so it is slightly less than fully 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 tool has 0 parameters, so the baseline for this dimension is 4. The description adds meaning by specifying the resource and the output fields, which is sufficient given the lack of parameters to document.

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 the action ('List'), the resource ('main characters in Taiping Nian'), and the output ('their scene counts'). It clearly distinguishes the tool from siblings like get_content_catalog (catalog-level) and search_scenes (scene-level).

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 description implies usage when character data is needed, but it does not explicitly state when to use this tool over alternatives or when not to use it. There is no mention of exclusions or comparison with the sibling tools.

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