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

Annotations already cover readOnly/destructive/idempotent/openWorld, and the description adds genuinely new context: external system changes are not automatically rolled back, and approval requirements are admin-configurable while business workflow approvals always apply. These are useful behavioral facts beyond the structured hints. It does not address failure behavior or idempotency (which is declared false), leaving a minor gap.

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?

Three succinct sentences with the purpose and the most important caveat (no rollback) front-loaded. Each sentence carries relevant signal with minimal waste.

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?

An output schema exists, so return values need not be explained, but the mutation touches an external connected system with a nested 0%-documented parameter object. The description covers side-effect and approval behavior but leaves parameter meaning and failure handling incomplete for a write operation.

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 0%, and the single 'data' object nests six undocumented fields (siteId, name, city, state, address, zipCode). The description only says 'Review all transmitted fields' and adds no meaning about required vs optional fields or formats, so it fails to compensate for the coverage gap.

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 clear verb+resource: 'Create/link this site's location in the existing incidentvault connection.' An agent can distinguish it from the many other create_*_linked_location siblings by the incidentvault target. It stops short of naming how it differs from sync_incidentvault_locations or preview_incidentvault_sync, so it is clear but not fully differentiated.

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 explicit when-to-use or when-not-to-use guidance is given, and no alternative is named despite siblings like sync_incidentvault_locations and preview_incidentvault_sync existing. The 'Review all transmitted fields' note is a caution, not a routing rule.

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