autofill_emit

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

No annotations exist, so the description must disclose behavioral traits. However, it only states that it builds a prompt, without indicating side effects, permissions, or whether it is read-only. The agent cannot infer if this tool mutates state or requires specific authorization.

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 a single sentence, which is concise but potentially under-specified. For a tool with one parameter, brevity is acceptable, but it sacrifices essential information. It could be improved while remaining concise.

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 the tool's complexity (1 param, output schema exists), the description is incomplete. It fails to explain how the prompt is used, its relationship to sibling tools like 'autofill_apply', or what happens after building. The output schema may partially compensate, but the description itself is lacking.

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?

The schema has 0% description coverage for the single parameter 'cluster_slug', and the description does not mention the parameter at all. It adds no meaning beyond the schema, leaving the agent to guess the parameter's purpose and format.

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 the tool builds a paper-note autofill prompt for an AI. It is specific about the resource (paper-note) and action (build prompt), but does not explicitly differentiate from siblings like 'autofill_apply' or other emit tools, which could confuse an agent.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. With many related sibling tools (e.g., autofill_apply, emit_assignment_prompt), the lack of usage direction is a significant gap.

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