agent_gallery_templates

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

Annotations already declare that the tool is not read-only, is open-world, not idempotent, and non-destructive. The description usefully clarifies that create makes a new agent from the template as-is, but it does not mention duplicate-creation behavior, permissions, or side effects, which leaves meaningful behavioral gaps.

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?

Front-loads the resource and then lists actions compactly with parenthetical details. The final sentence is a focused routing instruction, and there is no unnecessary text.

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?

For a two-action tool with no output schema, the description covers the essential purpose, actions, key create parameter, and the main alternative tool. It is not fully complete because it omits the mode parameter and gives limited detail on what listing returns beyond templateId.

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?

With only 40% schema description coverage, the description compensates for some key parameters by explaining action values, templateId's role in create, and that title/description are optional for the new agent. It does not cover mode at all and does not fully explain title/description semantics, so compensation is partial.

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?

Names the resource (ready-made agent templates in the gallery) and enumerates both actions with specific outcomes: listing templates with templateId and creating a new agent from a template. It also explicitly distinguishes itself from create_agent_from_template, so the agent can tell which tool to select.

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?

Gives clear action-level context for list vs. create and explicitly routes custom-agent creation to create_agent_from_template instead. It lacks a fuller when-not explanation for choosing gallery creation vs. other agent-creation paths, but the key alternative is named.

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