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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still contributes the auth-relevant fact that no account is needed and characterises the result as a visual gallery grouped by scene. It says nothing about freshness or how the listed accounts relate to output, keeping it below 5.

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?

Three sentences, front-loaded with what the tool surfaces and followed by the use case and access requirement. Each sentence earns its place, though the clause listing accounts and scene count could be tightened.

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 carries the burden of describing the return content and it does so: gallery by scene, accounts, scene count. Combined with the annotations covering read-only and open-world behaviour, an agent has enough to call and interpret it, though grouping/ordering of the gallery is unspecified.

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 takes zero parameters and schema coverage is 100%, so the baseline of 4 applies; there are no parameters for the description to disambiguate.

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?

States a concrete resource — the examples gallery organised by scene — plus the secondary returns (accounts where work is posted, scene count). That is more than a restatement of the title and lets an agent picture the payload. It stops short of naming a sibling to differentiate from, so it lands at 4 rather than 5.

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?

Gives a clear selection condition: use it when someone wants to judge results for themselves rather than read about them, which implicitly separates it from informational siblings like cmein_info or photo_advice. 'No account needed' adds a usable precondition. No explicit when-not or named alternative, so not a 5.

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