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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description does not need to repeat these. It adds valuable context about the output content: each decision includes the reason, profit at play, founder-attention cost, and input freshness. It also clarifies the scope ('every autonomous decision') and that it is an audit trail, not a live state. No contradictions with annotations.

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 longer than average but every sentence carries weight: it defines the tool, gives usage examples, and differentiates from a sibling. It is front-loaded with the core purpose ('THE tool for what the Freedom Engine has DECIDED') and then elaborates efficiently. No redundancy or filler, though it could be trimmed slightly without losing value.

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 read-only tool with no output schema, the description thoroughly explains what is returned (the audit feed with specific fields), how to filter (via routing), and when to use it. It also clarifies that it is the only source for decision history, covering all necessary context. The only omission is explicit mention of pagination, but the limit parameter in the schema covers that.

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 100%, so the baseline is 3. The description adds meaning by mapping the routing enum values to real-world scenarios (e.g., REFUSE_AND_SURFACE for faith/values content) and by explaining the purpose of the tool in relation to the parameters. This exceeds the schema descriptions, which are already clear, so a 4 is justified.

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 the tool's purpose: it provides the audit feed of every autonomous decision made by the Freedom Engine, detailing what was auto-run, teed up for approval, or refused. It uses specific verbs and resources and immediately differentiates from the sibling get_command_center_items. The purpose is unmistakable and distinguishes this tool from others in the family.

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 explicitly lists example queries that should trigger this tool (e.g., 'what did the engine do today', 'what did it auto-run') and names the alternative tool (get_command_center_items) with a clear explanation of when NOT to use this one (for open cards to act on). This provides direct, unambiguous routing guidance.

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