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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the description doesn't need to restate them. The description adds useful context that the result reports active vs staged-for-approval status, but it does not disclose the side effects of updating an existing manifest. No contradiction with annotations.

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 concise sentences, front-loaded with the primary action, with the second sentence adding unique output behavior. No redundant or filler content.

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 5 required parameters and no output schema, the description lacks parameter explanations and does not clarify what distinguishes a create from an update (e.g., existing connector_key). It also fails to mention the alternative create_connector_from_openapi, leaving an agent without enough information to invoke the tool reliably.

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?

The input schema contains no property descriptions, and the description does not explain connector_key, label, connector_type, transport, or functions. Despite the context signal claiming 100% schema coverage, the visible schema provides zero parameter documentation, so the description should compensate and does not.

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 ('Create or update') and resource ('Klarefi verification connector manifest'), making the core action clear. However, it does not differentiate from the sibling tool create_connector_from_openapi, which likely overlaps in purpose.

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 guidance is given on when to use this tool versus create_connector_from_openapi or delete_connector. The description implies a create/update operation but never states prerequisites, ordering, or exclusion conditions.

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