mark_moment

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Safe context snapshot' hints at non-destructive context capture, but it does not clarify whether this is a write operation, whether it requires permissions, or what side effects it has. The description omits critical details about persistence and reversibility.

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, concise sentence with no filler. It front-loads the core purpose immediately and earns its place by stating the tool's function without redundancy.

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 the tool has 7 parameters, no output schema, and no annotations, the description is too minimal. It does not explain what a 'build moment' is, what 'safe context snapshot' entails, or what the agent should expect as a result. The behavior is not adequately specified for correct invocation.

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% with all 7 parameters having descriptive text, so the description does not need to repeat parameter info. It also does not add extra semantic meaning beyond the schema, such as how parameters interact or typical usage patterns, keeping this at baseline.

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 identifies the action 'capture' and the object 'build moment', with 'safe context snapshot' adding a distinctive qualifier. This distinguishes it from sibling tools that export, list, or link moments, though the qualifier is somewhat vague.

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?

There is no guidance on when to use this tool versus alternatives like list_moments, link_moment_to_task, or export_timeline. It does not mention any prerequisites, conditions, or exclusions, leaving the agent without decision support.

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