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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true; the description usefully adds the auth scope requirement. However, for a tool flagged destructive it does not disclose what the write replaces — whether the prior preference is overwritten, whether the change is workspace-wide for all members, or what happens on an invalid integration name.

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?

Two sentences, front-loaded with the action, then the value source and auth requirement. No filler and nothing buried.

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 purpose, valid value source and permissions, which is the core an agent needs. It omits the mutating side effects implied by destructiveHint=true and any error behavior for unrecognized integration names, which matters for a write tool with no output schema.

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%, so all three parameters are already documented in the schema, including the same 'as returned by hub_list_integrations' note for preferredIntegration. The description adds only concrete example values (JIRA, CLICKUP, AIRTABLE, PM), which is marginal added value over the schema — baseline 3.

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 and resource: 'Set the workspace's preferred integration target.' The complement relationship with hub_get_preferred_integration and hub_list_integrations is inferable from the verb and the cross-reference, though neither sibling is named explicitly as an alternative.

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?

Gives clear preconditions: the value must come from hub_list_integrations and the caller needs workspace-settings:write scope. It does not state when-not to use it (e.g. single-integration or read-only contexts), so it stops short of full routing guidance.

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