layouts_pull

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

Adds detailed behavioral context beyond annotations: writes per-layout files, builds manifest, refuses to overwrite .tpl files, preserves non-tpl content. No contradiction with annotations (idempotentHint true is consistent).

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?

Dense but efficient: each sentence adds value. Front-loaded with purpose. Uses emphasis (REFUSES) to highlight critical constraint.

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?

Completely describes the tool's behavior, output (manifest schema), and error condition (refusal to overwrite). No output schema exists, so description covers all needed context.

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 covers both parameters fully. Description adds meaning by specifying the output structure (layouts/, components/, manifest.json) and the source of the 'site' parameter.

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 it fetches layouts and components, writes .tpl files, and builds a manifest.json. It distinguishes from the sibling tool 'layouts_push' by its fetch-and-write behavior.

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?

Provides clear conditions: use a fresh target_dir or clear it first, as the tool refuses to overwrite existing .tpl files. Does not explicitly compare to alternatives but implies its purpose.

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