team_sync

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the conflict-resolution mechanism ('last-write-wins timestamp comparison'), implying newer lessons overwrite older ones. But it does not disclose return behavior, failure modes (e.g., no team connection), or idempotency for what is clearly a mutating push operation.

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?

Three sentences, each earning its place: purpose+scope, conflict-resolution mechanism, and usage cadence. Front-loaded with the core action and free of 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?

For a moderately complex sync tool with no annotations and no output schema, the description covers purpose, conflict resolution, and invocation timing. However, it omits what the agent should expect after invocation (the absence of an output schema means the description carries that burden) and does not address error conditions or the risk of overwriting teammates' newer lessons.

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 tool has 0 parameters, earning a baseline of 4. The description adds meaning by implying the operation is a bulk sync of all lessons without filtering, which justifies the empty input schema.

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 opens with a specific verb+resource pair ('Synchronize team memory') and adds directional detail ('pull remote lessons from teammates and push local lessons'). This bidirectional framing clearly distinguishes it from siblings like team_init, team_status, lesson_save, and lesson_recall.

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?

Explicit when-to-use guidance is given: 'Run this periodically during a session to stay in sync with the team, or at session boundaries.' However, it does not explicitly name alternatives or state when not to use the tool, so it falls short of a 5.

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