skylight_create_category

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

With no annotations, the description carries full burden. It discloses that setting linked_to_profile and selected_for_chore_chart determines the member's role, and points to a follow-up tool for avatars. It does not detail side effects or auth needs, but adequately warns about optional configuration.

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?

Two concise sentences front-loaded with purpose, no wasted words. Every sentence adds essential guidance.

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?

While the description explains key parameters, it omits mention of the frameId parameter, which may be important if multiple frames exist. Given no output schema and 6 parameters, the description could be more complete about required context.

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 coverage is 83%, but the description adds value by explaining how to use linked_to_profile and selected_for_chore_chart together and where to source avatar_id. This goes beyond the schema's individual field descriptions.

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 'Create a category / family member on the frame' with a specific verb and resource. It distinguishes from sibling tools like skylight_update_category and skylight_delete_category by focusing on creation and providing guidance on optional flags.

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 gives explicit context on when to use the tool: 'Set linked_to_profile + selected_for_chore_chart to make it a full chore-chart member' and references skylight_list_avatars for avatar_id. It does not explicitly say when not to use it or compare with other creation tools, but the guidance is clear for typical use.

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