system_one_compact

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces these with 'never modifies host files' and 'returns a new transcript'. It adds the behavioral details of verbatim processing and output creation beyond the structural annotations. No contradiction exists.

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 concise sentence with no redundant phrasing. It front-loads the primary action, states the return result, and explicitly addresses side effects in a compact way. Every clause earns its place.

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 tool with a nested options object, seven undocumented parameters, and no output schema, the description is too thin to fully orient an agent. It omits what goal is for, how options affect behavior, and what the returned transcript contains beyond being 'new'. The complexity of the schema demands more explanatory context than a single sentence provides.

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 compensate, but it only loosely references 'supplied canonical messages' without explaining goal, options, or the nested option semantics. The nested options object contains seven tunable parameters with meaningful constraints, none of which are addressed. This is a clear gap for a tool with undocumented parameters.

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 specific verb, 'compact', a resource, 'supplied canonical messages', and a clear outcome: 'returns a new transcript'. It is understandable and distinguishable from siblings by the 'compact' operation, though the phrase 'tool-pair compaction' is jargon-heavy and does not fully define what the compaction accomplishes.

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 gives no guidance on when to use this tool versus any of the 13 siblings. It does not state preconditions, alternatives, or exclusions. The only contextual hint is 'supplied canonical messages', which implies a specific input source but is not actionable routing guidance.

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