sync_peer

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

No annotations are provided, so the description carries full burden. It mentions 'POST' implying mutation, but does not disclose whether the operation is destructive, idempotent, or what side effects occur. The behavior beyond sending a request is opaque.

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, efficient and front-loaded with 'Bounded outbound peer sync'. However, it packs technical details (POST path, env vars) without punctuation or structure, making it somewhat cryptic.

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 2 parameters and no output schema, the description omits critical details: success/failure behavior, response format, how 'limit' affects execution, and what 'observations' are synced. It is not sufficiently complete for an agent to use without additional context.

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 has 50% coverage (peer_id lacks description). The description mentions 'peer sync_target_user_id' but the schema only has peer_id, causing confusion. It adds little meaning beyond the schema: it says limit is optional, but the schema already has a minimum/maximum/description. The description fails to clarify the role of peer_id.

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 states it performs 'bounded outbound peer sync' via POST to a webhook for observations, which gives a specific verb and resource. However, it doesn't clearly distinguish from sibling sync tools like 'sync_entity_submissions' or 'sync_issues', and the jargon may be unclear to an agent.

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 lists prerequisites (environment variables, peer sync_target_user_id) and mentions an optional limit, but provides no guidance on when to use this tool versus alternatives. There is no explicit when/when-not or contrast with sibling tools.

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