Connect POS sales telemetry

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds context about the scaffold's contents, including privacy policy and PCI/PII safety notes, which is useful but does not disclose side effects such as where the scaffold is created or what files are modified. It does not contradict the annotations, and the added detail is moderate.

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 a single sentence that front-loads the action and uses a compact list to enumerate the scaffold's components. There is no redundant or filler text; every phrase contributes to understanding what the tool does.

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?

With 10 parameters, only 20% schema coverage, no output schema, and minimally descriptive annotations, the description is not sufficient for an agent to understand invocation details. It does not describe what the tool returns, how the scaffold is structured in the project, or how parameters influence the generated output. For a tool of this complexity, the description is too brief to ensure correct use.

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 only 20% (only 2 of 10 parameters have descriptions), so the description has a low baseline to work from. It mentions 'revenue buckets' and 'adapter source' which loosely correspond to revenue_bucket_count and adapter_url/adapter_mode, but it does not explain the meaning or relationships of most parameters (e.g., store_label, aggregation_window, metric_count). The description only partially compensates for the sparse schema, leaving many parameters underspecified.

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 a specific action ('Create a POS aggregate-telemetry scaffold') and identifies the resource ('POS sales telemetry'). It lists key components (sales metrics, revenue buckets, privacy policy, adapter source, PCI/PII safety notes) that distinguish it from sibling integration tools. However, the 'connect_' prefix is misleading since this is a creation/scaffold tool, and 'scaffold' could be more concretely defined.

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 implies usage by specifying the domain (POS sales telemetry), which differentiates it from sibling connect tools that target external services (e.g., connect_resolume_arena, connect_vmix_production). However, it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or conditions. The guidelines are inferred rather than explicit.

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