skylight_list_avatars

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

The description implies a read-only operation by stating 'List the preset avatar library.' No annotations are provided, but the description clearly indicates no side effects. It could further state 'read-only' explicitly, but the intent is 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 concise: two sentences with no wasted words. The purpose is front-loaded, and every sentence adds value.

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 description adequately explains the tool's purpose and how to use its output. Although there is no output schema, the description hints that avatar IDs are returned. It does not mention pagination or limits, but for a simple list tool, the information is sufficient.

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 input schema has no parameters (0 params), so the baseline score is 4. No additional parameter information is needed as the tool requires no inputs.

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 clearly states the tool's function: 'List the preset avatar library (emoji/icon images).' The verb 'list' and resource 'preset avatar library' are specific. It distinguishes itself from sibling tools like skylight_set_member_avatar which sets avatars, not lists them.

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 explicitly guides when and how to use the tool: 'Use an avatar id with skylight_create_category / skylight_update_category to set a member's avatar without uploading a custom photo.' It provides context for using the output and contrasts with an alternative (uploading a custom photo).

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