sdd-context-load

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

No annotations are provided, so the description must disclose behavioral traits, but it only states 'Load phase-aware governed context.' It does not describe whether the operation is read-only, whether it requires prior initialization, what 'governed' means in terms of permissions or data handling, or what the tool actually returns. This is insufficient for a tool with 6 parameters.

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 one short phrase and is concise, but it is under-specified. It is not tautological, but it reads more like a title than a useful explanation. Every word is used, but the content is too thin to earn full marks.

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 6 parameters, no output schema, and no annotations, this description is completely inadequate. It does not explain return values, side effects, parameter behavior, or how the tool fits into a workflow. An agent would have to guess or rely solely on the schema, which itself lacks descriptions for most parameters.

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 only 17% (only featureName has a description). The description itself mentions no parameters. While the schema provides enum values for mode and phase, it lacks descriptions for those enums and the remaining parameters like ifNoneMatch, includeUnapproved, and maxEstimatedTokens. The description does nothing to compensate for this low coverage.

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 'Load phase-aware governed context' uses the verb 'Load' and identifies a resource ('context'), but 'phase-aware governed' is vague jargon. It does not clearly distinguish this from sibling tools like sdd-requirements or sdd-init, which might also load specific context. It states a clear action but lacks the specificity needed to fully understand what the tool does.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where another sibling tool would be more appropriate. The agent is left without any usage context beyond the tool's name.

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