create_hosted_collector

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

No annotations are provided, so the description carries the full burden. It explains that hosted collectors are cloud-managed, which is useful behavioral context. However, it does not disclose potential side effects, permission requirements, idempotency, or error behavior, leaving gaps in transparency.

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 two sentences long and front-loads the purpose in the first sentence. The second sentence adds essential context about hosted vs. installed collectors without any filler. Every word earns its place.

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?

The tool is a simple create operation with a complete input schema and an output schema present. The description explains what a hosted collector is and when it is used. The only gap is the lack of information about permissions or response behavior, but the output schema likely covers the latter, making the description largely complete.

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 100%, so the input schema already documents all four parameters. The description adds no parameter-specific details beyond what the schema provides, so the baseline score 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 starts with a specific verb and resource: 'Create a new Hosted collector.' It clearly distinguishes this from installed collectors, and the context about HTTP sources, cloud-to-cloud integrations, and AWS polling sources further clarifies its intended use.

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 provides clear context on when to use this tool (for hosted collectors) and explicitly states that installed collectors cannot be created via API, which is an exclusion. It does not name a direct alternative, but that is appropriate since the sibling tools do not include another create-collector option.

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