chap.audit.submit_to_scitt

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

With no annotations, the description carries the transparency burden. It clearly discloses the two-mode behavior: submit when a SCITT service is configured and return statements for out-of-band submission when it is not. It does not, however, describe side effects like receipts, idempotency, or errors, so it is not a full 5.

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?

One efficient sentence carries the main path and the important fallback behavior without redundancy. It is easy to scan and front-loads the core action.

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?

The tool has no output schema, so the description should clarify expected return values; it only specifies the out-of-band return path. For the configured-submission path, it leaves the outcome and response shape unstated, so an agent cannot fully predict 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%, so the baseline applies. The description adds only a general framing of the range-of-audit-entries concept and does not need to compensate for missing parameter docs.

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 names a concrete action (build and submit) on a specific resource (audit entries / SCITT transparency service), distinguishing it from sibling audit tools like read or verify. The fallback phrase also clarifies the tool's exact role.

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 intended context is implied: use when you need to anchor or submit audit entries to SCITT. However, there is no explicit when-not-to-use guidance nor any mention of alternatives such as chap.audit.read or verify tools.

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