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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the authorization requirement ('Requires systems:write scope'), which is genuinely additive and not present in structured fields. However, it says nothing about cascade behavior or what happens to dependent systems/service areas that reference the class, which matters for a destructive operation.

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 short sentences, front-loaded with the action and resource, then the scope requirement. Nothing is padded, though the sentence 'Delete a system class by ID' is largely a restatement of the name and title.

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 single-parameter destructive delete with annotations already covering destructiveness and idempotency and no output schema, the description is minimally adequate. It omits the one thing an agent would most want to know about a destructive call: whether deletion cascades or fails when the class is still referenced.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'id' fully. The phrase 'by ID' adds no syntax, format, or constraint information beyond what the schema provides; baseline 3 applies.

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 specific verb (Delete) and resource (system class) plus the identifier used to target it, so the agent knows exactly what the tool does. It does not distinguish itself from the similarly named siblings (delete_project_system_class, delete_service_area_system_class), but the naming itself carries that differentiation.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as update_system_class for non-destructive edits. The only implicit signal is that deletion is the tool's job; nothing tells the agent under what conditions it should prefer this over another approach.

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