Update posture integration

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety and replay profile is covered. The description adds nothing beyond that: it does not say whether unmentioned fields are preserved (partial vs full replacement), whether the call is a full overwrite, or what authorization is required for credential changes.

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 verb and resource lead. It is slightly under-powered rather than padded, so conciseness is not the problem.

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?

There is no output schema and no annotations gap on safety, so the definition is minimally viable. However, for a mutation with four optional fields, the description never states that omitted fields retain existing values or that only integrationId is required, leaving the partial-update semantics to be reconstructed from the 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 description coverage is 100% and the schema already documents each field well, including that the secret is sensitive and omitted secrets are retained. The description's 'credentials or configuration' is a loose grouping of those parameters and adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 names a specific verb (update) and resource (posture integration) and narrows the scope to credentials or configuration, so an agent can distinguish it from create/delete/get posture integration siblings by name alone. It stops short of explicitly naming those siblings or stating what is not touched.

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 phrase 'an existing posture integration' implies the integration must already exist, but there is no explicit when-to-use, no prerequisites, and no routing to alternatives such as tailscale_create_posture_integration or tailscale_get_posture_integration. The agent must infer everything about invocation context.

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