configure_offline_sync

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

The description does add non-schema context (a required prerequisite workflow, and a claim of no state-table writes), which counts for something. But 'No state-table writes are performed' combined with 'UNSUPPORTED' conflicts with annotations declaring readOnlyHint=false and a '[Write]' marker — the safety profile the agent is given is internally inconsistent and unresolved.

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?

Three short sentences with the most important fact ('UNSUPPORTED') front-loaded; nothing is padded. The trailing '**[Write]**' marker is formatting noise rather than substance, keeping it from a 5.

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 stub/no-op tool with no output schema and fully documented params, saying 'unsupported, requires X' is close to sufficient. It still leaves the agent without a next step (what to call instead) and without resolving whether any write occurs, so it is adequate but incomplete.

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 description coverage is 100% (query, table, max_records each documented, with the 500 default stated), so the schema carries parameter meaning on its own. The description adds nothing about parameters, which is acceptable at this coverage level but no better than baseline.

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 never states what configuring offline sync actually does; its content is a negative status ('UNSUPPORTED') plus a precondition about a Mobile App Builder workflow. It does at least tell an agent the resource domain (offline configuration) and that the tool is not usable, which is more than a bare tautology, but the function itself is never described.

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?

'UNSUPPORTED' and 'requires a validated Mobile App Builder workflow' function as an explicit exclusion plus a prerequisite, which is useful routing signal. However, no sibling alternative is named — plausible substitutes like get_mobile_app_config, create_mobile_app_config, or list_mobile_app_configs are never referenced, so the agent is left to guess the replacement path.

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