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

With no helpful annotations (all false), the description carries the burden of behavioral disclosure. It discloses that duplicates are detected and rejected automatically, implying idempotent-like behavior without contradictions. It does not mention authentication, rate limits, or return value, but for a simple write operation the coverage is adequate.

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 five sentences, each serving a distinct purpose: stating the action, explaining the strategic value, listing use cases, providing a tip, and clarifying duplicate behavior. There is no wasted text; the information is front-loaded and efficiently organized.

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 three simple parameters, no output schema, and no nested objects, the description covers the tool's purpose, usage, and key behavioral trait (duplicate handling). It does not specify what the tool returns on success or failure, but for a capture operation the assumption of success is reasonable. The description is complete enough for an agent to use the tool effectively.

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% (all three parameters have descriptions). The description adds significant value: it advises passing the pillar by name if the ID is unknown, and for the 'content' parameter it warns against generalizing away details. These enrichments go well beyond the schema's baseline, fully compensating for any lack of parameter-level specifics.

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 action ('Save a piece of the user's first-party substance') and the resource ('into their ContentIn content bank, filed under one of their content pillars'). It distinguishes from sibling tools (generate_ideas, publish_post, etc.) which deal with generating, publishing, or scheduling posts, not capturing raw content.

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 tells when to use the tool: 'Use it whenever the user shares a real experience, a genuine opinion, a concrete number or result, or a process they use.' It also addresses a common concern by noting that duplicates are automatically rejected, making repeated captures harmless. This provides clear guidance without needing to list alternatives.

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