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

The description adds meaningful behavior beyond the annotations: the result reports whether the configuration is active or staged for operator approval, and checks remain open until connected. The annotations already declare the tool as destructive and non-idempotent, so the description does not need to repeat those safety facts. However, it could do more to clarify destructive effects.

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?

The description is front-loaded with the core create-or-update action and is composed of four compact, relevant sentences. Each sentence contributes operational information, with no obvious filler. It is slightly dense but well structured.

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 tool with no output schema, the description explains the key result states: active versus staged for operator approval. It also clarifies the staged credential flow and the open-checks condition. It leaves some gaps around destructive behavior and idempotency, which are partially covered by annotations.

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 reported as 100%, so the schema already carries the primary parameter documentation burden. The description adds useful semantics for connection_status and credentials, but does not explain the required fields connector_key, label, connector_type, transport, or functions. This is adequate given high schema coverage, but not a strong supplement.

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: 'Create or update a Klarefi verification connector manifest.' This clearly identifies the operation and domain. It does not distinguish itself from the close sibling create_connector_from_openapi, so it falls short of full sibling 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?

The description gives concrete usage instructions: set connection_status to not_connected and omit credentials to add now, then upsert with connected and credentials later. It also explains that checks remain open until connected. It lacks explicit guidance on when to use this versus create_connector_from_openapi or delete_connector.

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