Synchroniser tout le site

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

Annotations already flag readOnlyHint=false and destructiveHint=false. The description adds the key behavioral detail that the operation runs 'En tâche de fond' (in the background), which is not present in annotations. It also clarifies the data-flow direction for each action, but does not disclose how the background task can be monitored or whether existing data is merged or overwritten.

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 concise sentence with em-dash separators: it states the purpose, defines both actions, mentions background execution, and includes the HTTP endpoint. Every part earns its place with no repetition or filler.

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 background operation with no output schema, the description leaves a notable gap: it does not say how the agent will know when the sync finishes or how to track progress. A sibling tool 'getTask' exists and could be the intended follow-up, but the description does not mention it. For a two-parameter bulk sync tool this is the main missing piece.

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% because the 'action' parameter has an enum but no description. The tool description compensates by explaining what 'import' and 'push' actually do. 'siteId' is already described in the schema as an encoded hashid, and the endpoint string reinforces its role.

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 the tool synchronizes the entire site and breaks down the two specific actions (import = bring CMS content into GPSEM; push = send followed pages to CMS). This clearly identifies a bulk operation distinct from the individual page-level siblings like pushPageToCms and pullPageFromCms.

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 gives clear context for when to use each action via the import/push definitions, and the phrase 'tout le site' makes the bulk scope explicit. However, it does not explicitly name alternatives or state when NOT to use this tool in favor of single-page operations.

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