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 largely covered. The description does add real value by disclosing the required auth scope, but it says nothing about cascade effects (e.g., whether associated floors, assets, or project links are removed) or whether the delete is soft or hard.

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 tight sentences: the action and target are front-loaded, and the scope requirement follows. Nothing is padded or redundant.

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 destructive, no-output-schema tool, the essentials (what it deletes, the identifier, the required scope) are present, and annotations carry the destructive/idempotent semantics. It falls short on the consequences of the operation — cascade behavior and confirmation of permanence — which an agent should know before invoking a delete.

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, fully documented in the schema (uuid format, pattern, description 'Building ID'), giving 100% schema coverage. The description's 'by ID' adds no meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource ('Delete a building by ID'), so the agent immediately knows what the tool does. The resource name itself distinguishes it from the many other delete_* siblings, but the description offers no further differentiation (e.g., what 'building' encompasses versus 'site' or 'project_building').

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?

It gives one concrete precondition ('Requires buildings:write scope'), which tells the agent whether it is even eligible to call the tool. However, there is no guidance on when to use this versus alternatives such as update_building or delete_project_building, nor any warning about irreversibility or dependent records.

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