polarity_capture_turn

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

With no annotations, the description fully discloses behavior: it runs an extractor, creates nodes if warranted, returns node IDs, and is safe to call. Could mention potential graph mutations more explicitly, but overall transparent.

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?

Front-loaded with the critical instruction, each sentence adds value—explaining why, when, and how. No redundancy or fluff.

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?

Provides full context: user installed cosmos for persistence, tool returns node IDs, extractor behavior, and when to skip. Covers all aspects needed for correct usage despite no annotations or output schema.

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?

Describes user_text, assistant_text, and source with usage examples, but does not explain max_observations. Since schema coverage is 0%, this is a minor gap, but the description compensates well for most parameters.

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 explicitly states the tool's purpose: capturing conversation turns for persistence into the user's cosmos graph. It distinguishes from siblings by focusing on raw exchange handover, not querying or recording specific events.

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?

Provides explicit guidance: call at end of every substantive exchange, skip trivial ones, pass raw text without filtering, and use source to identify the client. Explains consequence of not calling and that it's cheap to invoke.

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