layouts_pull

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

Beyond annotations, the description discloses refusal to overwrite existing .tpl files and preservation of non-tpl content. It adds context about writing behavior. The idempotentHint=true annotation is slightly contradicted by the refusal behavior, but the description explains it, so no major contradiction.

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?

Three concise sentences: first covers core function, second explains refusal, third clarifies edge case. No redundant words, well front-loaded.

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 low complexity (2 required params, no output schema), the description covers main behavior and constraints. However, it does not describe what the tool returns upon success or failure, which is a gap for agent invocation.

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% with basic descriptions. The description adds meaning by explaining that target_dir receives layouts/, components/, and manifest.json, clarifying the output structure. This adds value beyond the schema alone.

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 every layout and component from /layouts, writes .tpl files to specific directories, and builds manifest.json. It uses specific verbs and resource details, distinguishing it from siblings like layouts_push which does the reverse.

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 explicitly tells the agent when to use (fresh location) and when not to (if .tpl files exist), with clear refusal behavior. It does not name alternatives, but the sibling list includes layouts_push, implying the reverse operation. Missing explicit comparison to siblings.

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