validate.sscc

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Validate' and 'Deterministic,' but does not explain the return value (e.g., boolean, error messages) or whether any external calls are made. This leaves significant gaps for an agent.

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 extremely concise with two sentences, no extraneous information. It front-loads the key action and format, then provides context.

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?

For a simple validation tool with one parameter and no output schema, the description covers the purpose and format adequately. However, it lacks information about the output (e.g., does it return a boolean or an object?), which is essential for an agent to understand how to use the result.

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 100% for the single parameter. The tool description adds the check digit and logistic unit context, but does not provide additional format details or examples beyond what the schema states.

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 it validates a GS1 SSCC code, explaining the format (18 digits with mod-10 check digit) and the purpose (logistic units for shipping/ASN). It distinguishes itself from sibling validation tools by specifically naming SSCC and its context.

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 context on when to use the tool (for SSCC codes in shipping/ASN) and notes it is deterministic. It does not explicitly list when not to use or alternatives, but the sibling group implies other tools for different identifiers.

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