skylight_set_member_avatar

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

Beyond the destructiveHint annotation, the description adds critical behavioral details: the dry-run mode (no network call, returns preview with resolved path and mime), the need for confirm to proceed, and the multipart/form-data upload format. This fully prepares the agent for safe invocation.

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 with two well-structured sentences. The first sentence states the core purpose; the second provides usage guidance and behavioral details. No unnecessary words, every part serves a purpose.

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?

Given the tool has 4 parameters, no output schema, and basic annotations, the description covers all essential aspects: purpose, alternative methods, detailed parameter behavior (confirm), upload format, and dry-run response. It is complete enough for correct invocation.

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 description enhances the schema by explaining the confirm parameter's dual behavior (preview vs upload), noting image_path must be absolute, and specifying supported file formats. It adds semantic context beyond schema descriptions, which is especially valuable for the confirm parameter.

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 sets a family member's avatar using a local image file, and explicitly distinguishes from preset emoji avatars by referencing alternative tools. It uses a specific verb ('Set') and resource ('family member's avatar').

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?

Provides explicit guidance: when to use this tool (custom photo), when to use alternatives (preset emoji), and explains the dry-run vs actual upload behavior based on the confirm parameter. The description tells the agent exactly how to invoke it correctly.

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