metapod

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description usefully adds that the host — not this tool — executes the returned packet, which is consistent with readOnlyHint. However, it says nothing about what the packet contains, latency, or how the request is interpreted.

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?

Two short sentences, the transformation outcome is front-loaded, and there is no filler. It is efficient, though the opening meta-phrasing is slightly awkward.

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 no output schema, an opaque tool name, an undocumented sole parameter, and no sibling differentiation among eleven related tools, the definition omits too much for an agent to confidently select and invoke it.

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% for the single required 'request' parameter, so the description carries the burden. It only restates it as a 'raw request' without saying what form that takes (natural language? structured? size/format expectations), adding almost nothing beyond the schema's maxLength=200000.

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 names the transformation (a request into System and Task Prompts), so the verb+output are identifiable, but 'Prepare Metapod' is self-referential and opaque — it never says what Metapod is or how it differs from prompt-related siblings like tasker, prompt_pipeline, or brian_spillner.

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?

There is no guidance on when to call this versus the many prompt/pipeline siblings, no prerequisites, and no exclusions. The agent is left to infer the triggering condition from the phrase 'raw request' alone.

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