codix.prompt.generate

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only mentions 'Smart Context Mode' without explaining what that entails, and omits any details about side effects, external calls, authentication, or output format. This is a significant transparency gap.

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, front-loaded sentence that conveys the core action and key differentiator. Every word earns its place, with no filler or redundant content.

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 has four parameters, no output schema, and no annotations, the description is insufficiently complete. It doesn't explain what 'Smart Context Mode' means, how the input brief is used, what the output prompt looks like, or how parameters like output and targetAgent affect behavior. This is a substantial gap for effective tool usage.

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%, so the description must explain parameter meaning. It does not mention any of the four parameters (brief, output, maxTokens, targetAgent), nor does it imply them beyond the generic notion of a prompt generation. The description adds no value to the schema's parameter definitions.

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 uses a specific verb ('Generate') and resource ('compact agent prompt') and further distinguishes the tool with 'Smart Context Mode instead of long pasted docs,' which differentiates it from sibling tools like codix.context.smart and codix.docs.generate. The purpose is unambiguous.

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 phrase 'instead of long pasted docs' provides clear context that this tool is appropriate when a concise prompt is needed and long documentation should be avoided. While it doesn't name specific alternative tools or exclusions, it gives a clear situational cue.

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