Sync the projectpad over git

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

The description goes far beyond the annotations by detailing observable behavior: status output fields, push commit-and-retry semantics, pull rebase behavior, rate-limit bypass for pull, auto-sync behavior, and monorepo handling. This substantially enriches the sparse annotation set and gives an agent a reliable model of side effects.

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 dense but every sentence earns its place: the first sentence explains the three actions, the second provides usage context and selection criteria, and the third covers an important edge case. It is front-loaded and well structured.

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 no output schema, the description covers action semantics, when to use it, what status reports, push/pull failure behavior, rate-limit effects, and monorepo safety. Nothing essential for an agent to select and invoke the tool correctly is missing.

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 only 50%, but the description compensates by explaining each enum value of 'action' in behavioral terms and clarifying that 'project' is required for pull while status/push cover all pad repos. It adds meaning beyond the bare parameter names.

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 and resource ('Explicitly sync the board's pad repo(s)') and then enumerates the exact actions (status, push, pull). It clearly distinguishes this tool from generic git configuration or commit tools by scoping it to pad repos and manual sync.

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 explicitly states when the tool is unnecessary ('Automatic syncing normally makes this unnecessary') and when it should be used: to verify sync state, force a flush before ending a session, or recover after being offline. This is direct guidance about when to invoke the tool relative to the automatic-sync alternative.

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