sdd-steering-custom

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the creation action and offers no information about side effects, file system changes, overwrite behavior, or relationship to other sdd tools. This is insufficient for a tool that appears to generate artifacts.

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 short sentence, which is technically efficient, but it is under-specified rather than concise. A tool with four parameters and custom behavior needs more than a purpose statement to be useful, so the brevity is not appropriate.

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 lack of an output schema, annotations, and parameter descriptions, the single-sentence description is far from complete. It fails to address the tool's input requirements, behavior, or expected outputs, making it inadequate for correct 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 description coverage is 0% for four parameters (topic, fileName, filePattern, inclusionMode), and the description does not compensate by explaining any parameter meanings or relationships. The agent must rely solely on parameter names and the enum for inclusionMode, which is inadequate.

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 'Create a custom steering document' uses a specific verb ('Create') and resource ('custom steering document'), clearly distinguishing it from the sibling tool 'sdd-steering' which likely handles standard steering documents. The word 'custom' is a meaningful qualifier that sets it apart.

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 like 'sdd-steering'. The description does not mention prerequisites, conditions, or scenarios where a custom steering document would be needed, leaving the agent to guess.

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