crosspad_apps_sync

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

Annotations declare destructiveHint=true, and the description says the tool rebuilds the manifest from disk state, which conveys the manifest gets overwritten. However, it doesn't add detail about what happens to manifest entries without corresponding submodules (are they removed?), or any confirmation/rollback behavior. Given the destructive annotation, the description adds minimal behavioral context beyond the annotation.

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?

A single, densely informative sentence with the parenthetical clarifying the rebuild-from-disk behavior. Zero wasted words, front-loaded with the main verb and object.

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 single-param tool with a complete enum schema and an output schema present, the description covers the core operation well. The only gap is behavioral detail on destructive outcomes, but annotation + description together make the primary behavior clear. Output schema handles return values, so the description doesn't need to.

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 covers 100% of parameters, with platform fully enumerated (idf/pc/arduino) and each enum value described. The description repeats 'platform' as the target concept but doesn't add semantic meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states a specific verb+resource ('Sync a platform's apps.json manifest with existing submodules') and adds the clarifying note '(rebuild manifest from disk state)'. It distinguishes this from related sibling tools like crosspad_apps_install/remove/update/list, which operate on the manifest/apps in a different direction.

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 implies it's used when submodules exist on disk but the manifest is out of sync, though it doesn't explicitly spell out when to use it vs alternatives like crosspad_submodule_update or crosspad_apps_update. Context is inferable but no exclusions or explicit alternatives are named.

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