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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation profile is covered structurally. The description adds one genuinely useful behavioral fact not in annotations: it requires the systems:write scope. It says nothing about what happens on duplicate names or failure handling, so it is adequate but not rich.

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 compact sentences, front-loaded with the action and resource, with the scope requirement placed at the end. No filler; every clause contributes.

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 simple two-parameter create tool with annotations and a fully covered schema, the definition is close to sufficient. The notable gap is disambiguation from create_project_system_class and create_service_area_system_class, which an agent could easily pick instead of this global variant.

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 100%, so both parameters (name, description) are already documented by the schema and a baseline of 3 applies. The examples of class names add mild illustrative color but no additional parameter semantics such as uniqueness constraints or length guidance.

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 ('Create a new system class') and even clarifies the concept with concrete examples ('HVAC & Mechanical', 'Material Handling'), so an agent understands what a system class is. However, it does not distinguish this top-level class from the scoped siblings create_project_system_class and create_service_area_system_class, leaving real ambiguity in a crowded namespace.

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 no when-to-use guidance and names no alternatives. With three near-identical 'create ... system class' variants in the sibling list, some routing guidance would be especially valuable, but none is offered.

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