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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds the required write scope ('project_system_classes:write'), which is genuine value, but says nothing about failure modes (e.g., whether dependent records block deletion) or what the response contains.

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, zero filler, with the action and identifier front-loaded and the prerequisite scope stated directly after. Nothing could be trimmed without losing information.

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 full schema coverage and no output schema, the description covers what, how to identify the target, and the auth requirement. The only real gap is the absence of any note on cascade or dependency behavior when removing a class from a project.

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, including format and UUID pattern, so the schema carries the documentation burden. The description only echoes 'by ID' and adds no format or semantic detail beyond the schema.

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 and resource ('Remove a system class from a project') plus the lookup key ('by ID'). It does not, however, distinguish itself from very similar siblings such as delete_project_system, delete_system_class, or delete_service_area_system_class, which an agent could plausibly confuse.

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 mentions the required scope, which implies an authorization precondition, but gives no explicit when-to-use or when-not-to-use guidance relative to the near-identical delete siblings in this large toolset.

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