datacore_capture

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

With no annotations, the description must disclose behavioral traits. It only states the basic function and proactive intent, omitting side effects, authentication needs, rate limits, or what the tool returns. The agent lacks context on outcomes like confirmation or storage.

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 sentences precisely describe the function and usage context without any redundant or verbose content. Front-loads the core action and then provides proactive guidance.

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 4 parameters and no output schema, the description is adequate but incomplete. It does not clarify the difference between journal and knowledge entries, optionality of tags, or the output after capture. More detail would improve completeness.

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?

The schema covers 75% of parameters with descriptions. The description adds context that 'journal' and 'knowledge' are options for the type parameter, but otherwise adds no meaning beyond the schema. This meets the baseline for high 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?

The description clearly states the tool captures 'a journal entry or knowledge note,' specifying the resource type. It further guides proactive use for recording important decisions, meetings, and events, distinguishing it from sibling tools like search and ingest.

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 suggests proactive use for important events but does not explicitly state when not to use the tool or mention alternatives like datacore_search for retrieval. The guidance is implied, not definitive.

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