catalog_run_agent

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

With no annotations provided, the description carries the full burden. It discloses that the run is asynchronous, results are applied in the background, and that the API cannot stop a running agent. This provides important behavioral context, though it omits details like error handling or what happens if the agent is already running.

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 concise at four sentences, front-loaded with the core purpose, and contains no redundant information. Every sentence adds value.

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 the tool's complexity (async agent run) and the presence of an output schema (not shown), the description covers the key aspects: asynchronous execution, background application, and the inability to stop a running agent. It is fairly complete, though it could mention the output schema or return values briefly.

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 there is only one required parameter (agent_id) with a description in the schema. The description adds a reference to catalog_list_agents for finding IDs, but this provides minimal added value beyond the schema. 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 clearly states the tool starts an asynchronous catalog discovery agent run. It specifies the verb 'start' and resource 'agent run', distinguishing it from related siblings like catalog_get_agent_history (for tracking) and catalog_list_agents (for listing).

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 explains when to use the tool (to trigger crawling and refreshing metadata) and provides guidance on tracking completion via polling. It also notes a limitation (cannot stop a running agent), but does not explicitly discuss when not to use it or alternative tools for synchronous operations.

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