shared_margin_capture

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention any side effects, authorization needs, idempotency, or what happens to existing data. The poetic description adds no behavioral context beyond the action of saving.

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 sentence, making it concise, but it is vague and poetic rather than informative. It is front-loaded but at the cost of clarity, wasting the opportunity to provide useful 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?

For a tool with 9 parameters, no annotations, and no output schema, the description is severely lacking. It does not explain the tool's role in the shared margin workflow, how it relates to sibling tools, or what the output looks like. The agent cannot fully understand its purpose from this description alone.

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 description coverage is 44%, and the tool description does not add any parameter explanations. The description does not clarify what 'anchor', 'excerpt', or 'question' mean in the context of shared margins, nor does it help the agent understand how to populate these fields.

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 uses poetic language ('anchored moment', 'paused, noticed, responded, or kept wondering') that hints at capturing an interaction, but it does not clearly state that this tool creates a margin note or annotation. It vaguely implies a save operation but lacks specificity about the resource being created.

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?

No guidance is provided on when to use this tool versus its siblings (shared_margin_begin, export, finish, trail). The description does not specify any context, prerequisites, or alternatives, leaving the agent to guess the appropriate tool.

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