save_brain_learnings

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

No annotations provided, so description bears full burden. It discloses persistence and reuse of audience filters, but omits side effects, overwrite behavior, error handling, or authorization requirements. Minimal behavioral context.

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?

Two short sentences with zero redundancy. Every word serves a purpose: verb, resource, prerequisite, and a critical caveat.

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 25 parameters, no output schema, and no annotations, the description is too lean. Doesn't explain 'Brand Brain notes,' how slices are formed, response expectations, or parameter interactions.

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 4% (only one param documented). Description adds no explanation of the 25 parameters beyond a vague reference to 'same canonical audience filters.' Fails to compensate for the low schema coverage.

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 clearly states 'persist' as verb and 'Brand Brain notes' as resource. Explicitly links to sibling tool get_brain_learnings, distinguishing save vs. read operation. The phrase 'reviewed get_brain_learnings slice' sets clear scope.

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?

Implies usage after reviewing a slice from get_brain_learnings. The causality caveat warns against misinterpretation. No explicit when-not or alternatives, but the context is clear enough for an agent.

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