context_compaction_verifier

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

No annotations and no output schema, so the description carries the full behavioral burden, yet it does not state whether the tool is read-only, how it compares inputs, what it returns, or whether it mutates state. It only describes the audit goal, leaving operational traits undisclosed.

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 sentence, front-loaded with the verb and scope; no filler. It is appropriately sized for the amount of information it delivers.

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 two-string verifier with no annotations and no output schema, the description is thin: it omits parameter guidance, output/result semantics, and any indication of how to interpret failures. An agent would need to guess how to assemble original_context vs. compacted_summary and what the tool returns.

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 coverage is 0% and the schema itself has no parameter descriptions. The description loosely maps the two inputs to pre- vs. post-compaction summaries, but it does not explain what each string should contain, formatting expectations, or how the comparison uses them.

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?

Names a specific verb (Audits) and resource (pre-compaction vs. post-compaction state summaries) and states the target invariants (zero dropped constraints, wallet addresses, IDs). The sibling set contains no other compaction verifier, so the agent can distinguish it without extra help.

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 when-to-use or when-not-to-use guidance, and no alternatives are mentioned (e.g., hallucination_auditor or agent_schema_enforcer). The intended context is only implied by the tool name and purpose.

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