run_knowledge_connector

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

Annotations indicate mutability (readOnlyHint=false) and no idempotency. The description explicitly says 'MUTATING' and explains the side effect (creates/updates chunks). It does not mention if the operation is asynchronous or any rate limits, but the annotations cover the basic safety profile.

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 that front-load the main action and immediately follow with the critical behavioral note about dryRun. No redundant or extraneous information.

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?

Given no output schema and a mutation operation, the description adequately explains the purpose and dry run behavior but does not mention whether the run is synchronous/asynchronous, what the response format is, or any prerequisites (e.g., connector must be enabled). Some gaps remain.

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 coverage is 100% and all parameters have descriptions. The description adds no new information beyond reinforcing the dryRun default. With complete schema coverage, the baseline is 3.

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 clearly states the specific action: 'Triggers a Cognigy.AI knowledge connector to run immediately' and explains what it does ('Pulls content... creates/updates knowledge chunks'). It distinguishes this from other knowledge connector tools (list, get, create, etc.) that don't initiate runs.

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 implies that this tool is for triggering a connector run, and includes the important note about dryRun. However, it doesn't explicitly state when to use this versus alternatives (e.g., if there were other run-like tools) or any prerequisites.

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