setConnectionPageConfig

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

Discloses making the app MANAGED, validation behavior (warnings for unknown keys not blocked), post-write action ('run regenerateConnectionPageFile'), and error handling (401 with account_required hint). No annotations present so description carries full burden.

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?

Somewhat long but every sentence adds essential information; front-loaded with key purpose. Could be slightly more structured but remains efficient.

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?

Covers prerequisites, behavior, post-write action, and error cases. Lacks explicit return value description, but for a mutation tool without output schema, this is acceptable. Complete enough given complexity.

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 100%, but description adds context: explains config structure, that omitted fields become null and SDK fills defaults, and identifies appPackage as bundle id. Adds meaningful value beyond schema.

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 the tool persists ExtentosConnectionPage config (theming and section visibility) and distinguishes it from siblings like getConnectionPageConfig (read) and regenerateConnectionPageFile (post-write mirror).

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?

Explicitly says when to use ('to author/update connection-page theming'), when not to (just to read, use getConnectionPageConfig), and prerequisites (linked Extentos account, login hint).

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