lc_preview_push_config

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

No annotations provided, so the description must carry full burden. It does not disclose whether this tool is destructive, whether it actually pushes changes or just simulates, or any permissions required. The term 'preview' implies non-destructive, but it's not confirmed.

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 only one sentence, but it is under-specified and lacks structure. Conciseness should not come at the cost of clarity; here, it fails to convey necessary 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?

With 16 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain key concepts like 'org IaC configuration' or 'ext-infrastructure', and how the various sync parameters interact. The tool is likely complex, but the description is minimal.

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 0%, meaning parameter descriptions are empty. The description adds no meaning to any of the 16 parameters, including critical ones like 'config' (an object) and many boolean sync flags. The agent cannot understand what each parameter does from the description.

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 'Preview pushing org IaC configuration through ext-infrastructure' gives a general idea but is vague. It mentions 'preview' which suggests it's a dry-run, but it's not explicit. The name and sibling tools indicate it's one of many preview operations, but the description doesn't distinguish what this specific preview does.

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 on when to use this tool versus alternatives. The sibling list includes many preview tools (e.g., lc_preview_set_config, lc_preview_create_org), but the description provides no context for differentiation.

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