ck_engineer_mirror

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

Annotations already declare readOnlyHint=true. Description reinforces 'Read-only' and adds important nuance: 'Surfaces how the human is steering — not how the agent is performing.' No contradictions.

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?

Description is comprehensive but not overly verbose; each sentence adds value. Could be slightly tighter but still well-structured with front-loaded purpose.

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?

Given high schema coverage, output schema presence, and thorough annotations, description covers all key aspects: what tool does, what to pass, and the nature of output (focus on human steering).

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 describes session_id fully. Description adds practical usage context: 'Pass session_id to inspect the current session's reflection view.'

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?

Description explicitly states 'Engineer-facing daily mirror' and lists specific components (plans, approvals, outcomes, patterns, signal). Clearly distinguishes from siblings by focusing on 'how the human is steering' rather than agent performance.

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?

Clear that session_id is required to inspect current reflection view. No explicit exclusion or guidance on when not to use, but context implies for human steering review.

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