memo_unified_briefing

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

The description declares 'Read-only' and 'Load', which align with annotations (readOnlyHint=true, destructiveHint=false). It adds context about loading from 'durable and operational state'. No contradictions; the description complements the annotations well.

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 concise: three sentences with no redundancy. The first sentence states purpose, second gives usage timing, third explains parameters. Front-loaded and efficient.

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 good annotations and presence of output schema, the description sufficiently covers what an agent needs: purpose, usage, parameter semantics. No gaps left.

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?

Despite 0% schema description coverage, the description explains both parameters: 'cwd' biases project context, 'source' attributes consult logs. This provides necessary meaning beyond the raw schema.

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 specifies the verb 'Load' and the resource 'compact startup briefing', clearly stating what the tool does. It also distinguishes the tool from siblings by mentioning it loads from 'durable and operational state' and is meant for grounding tasks before decisions.

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 says 'Call before deciding or answering so prior durable facts can ground the task', providing clear context on when to use. It does not mention exclusions or alternatives, but the usage guidance is strong.

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