skylight_delete_category

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

With no annotations, the description carries the full burden, but it only states that deletion happens. It does not disclose irreversibility, what happens to the member's items if reassign_to_category_id is not provided, auth requirements, or cascading effects. The schema description of reassign_to_category_id hints that items would otherwise be orphaned, but the main description offers no such transparency.

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 short sentence with no wasted words, which is structurally clean. However, it is under-specified: it contains almost no behavioral or parameter context, so the brevity is not fully appropriate for a destructive operation with three parameters.

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?

For a delete tool with no annotations, no output schema, and three parameters, one sentence is insufficient. It does not cover deletion consequences, reassignment behavior, or how this tool relates to the many sibling member/category tools. The schema's reassign_to_category_id description provides one useful detail, but the tool definition as a whole leaves important context missing.

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 description coverage is only 33%, so the description needed to compensate for undocumented 'id' and 'frameId' parameters, but it does not explain either. The phrase 'category / family member' indirectly suggests that 'id' identifies a member/category, providing a little semantic value beyond the bare schema, but most parameter meaning is still left to inference.

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 names the action ('Delete') and the resource ('category / family member'), so an agent knows what the tool does. It is slightly ambiguous whether category and family member are synonyms or two resource types, but the tool name and sibling set make the intent reasonably clear.

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?

There is no guidance on when to use this tool instead of related operations such as skylight_update_category, skylight_remove_user, or skylight_update_family_member, and no mention of prerequisites or exclusions. The only hint is the verb 'Delete', which is implied usage at best.

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