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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, but the description adds real value beyond them: approval depends on live org/connection risk rules, authorization windows expire after use, and provider record text is untrusted data (a prompt-injection warning). These are behavioral facts an agent could not get from the structured fields. It does not clarify what happens to a prepared-but-unexecuted write, keeping it from a 5.

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?

Front-loaded with the key semantic (prepare, not execute) and dense with relevant info; every clause carries weight. The docs/policy pointers and API name are slightly tacked-on but don't bloat it.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. However, with only 17% schema coverage across 6 parameters and no description of what body/query/pathParameters should contain, the definition is not complete enough for an agent to construct a valid call confidently.

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 only 17% — only clientRequestId is documented — and the description adds no meaning for endpointId, body, query, pathParameters, or files. For a 6-parameter tool with nested objects, the description should compensate for the coverage gap and does not.

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 outcome: "Prepare an immutable write without executing," which cleanly separates it from the execute step in the two-phase pattern. It names the target API (SmartShifts organization workforce API), but does not distinguish it from sibling system_write, leaving that ambiguity for an agent comparing the two.

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?

It says sensitive, bulk and destructive actions require approval by default, which hints at the governance context for use. But it never states the workflow sequencing (prepare here, then call system_execute_write) or when to choose system_write instead, so usage is only implied.

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