save_brief

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

With no annotations provided, the description carries the full burden of disclosing side effects. It specifies the output path and accepted period formats, which is useful, but it does not mention overwrite behavior, validation of inputs, or any return value. For a write operation, this is a moderate level of transparency.

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, efficient sentence that is front-loaded with the action and destination. Every word adds value, with no redundancy or filler.

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 simple 2-parameter tool with no output schema, the description is nearly complete. It provides the destination path and accepted period formats, which covers the core requirements. Minor omissions like overwrite behavior do not significantly hinder understanding for basic use.

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?

Even though schema description coverage is 0%, the description compensates by explaining both parameters: 'period' is given explicit format options (YYYY-MM, 'all', 'lastN'), and 'markdown' is described as 'composed brief markdown' indicating the content type. This adds meaning beyond the bare 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 clearly states the verb (Save), the resource (composed brief markdown), and the destination (data/briefings/<period>.md), making the tool's purpose unambiguous. It also distinguishes itself from sibling tools like save_user_note by specifying briefs specifically.

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 implies when to use the tool (when saving a composed brief) but does not explicitly contrast it with alternatives like save_user_note or provide exclusions. It provides enough context for a straightforward save operation but lacks explicit guidance.

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