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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds the concrete scope of the mutation (schedule on/off plus frequency), but says nothing about prerequisites (e.g. a connected Shopify platform), what happens to scheduled jobs when disabling, or the resulting state.

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 front-loaded sentence with no filler; the action, target and options are all packed into one readable clause.

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 3-param settings toggle with annotations and no output schema, the description covers the action and the two configurable dimensions. Remaining gaps (param interdependence, platform connection precondition) are modest but real.

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 33% – only 'site' has a description. The description compensates for 'enabled' via 'on or off' and restates the frequency options that already live in the enum. It does not clarify that 'site' is required, whether frequency is ignored when enabled is false, or how the two optional params interact.

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?

States a specific verb+resource: toggling scheduled Shopify product sync and setting its frequency. An agent can distinguish this from get_product_sync_status and sync_products (the latter is an on-demand sync, not schedule configuration), though the description never names those siblings explicitly.

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?

No when-to-use, when-not-to-use, or alternative guidance. With siblings like sync_products and get_product_sync_status nearby, the agent gets no signal about which of the three to select for a given intent beyond the word 'scheduled'.

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