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

Goes well beyond the annotations: sensitive/bulk/destructive actions require approval by default, queued requests are immutable, uncertain results must not be retried, and record text is flagged as untrusted data (prompt-injection defense). It does not say what exactly an approval queue returns or how authorization decisions surface in the response.

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?

Sentences are dense and mostly load-bearing, but the operation itself is never front-loaded — the first clause is about connection state, not about what gets written. Jargon like 'live connection' and 'immutable request' is used without definition.

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?

With a nested body object, a files array, path/query params, and only 17% schema coverage, the description should explain how to identify an endpointId and what body should contain. It relies entirely on external docs (/mcp, smartshifts://policy) without describing the payload model.

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 only 17% of 6 parameters; only clientRequestId is documented in the schema, and the description adds nothing about endpointId, body, query, pathParameters, or files. For a generic write endpoint where endpointId is the sole required parameter, this is a major gap.

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 describes the authorization/queueing behavior but never states the core operation in a verb+resource form; the only clue is 'Target API: SmartShifts organization workforce API' plus the title. It also fails to differentiate from siblings system_execute_write and system_prepare_write, which sound like near-identical write paths.

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?

Explicit conditional routing is given: execute when live connection and org rules permit automatic authorization, otherwise queue for the human approver, plus 'Never retry uncertain results.' However, it gives no guidance on when to pick this over system_execute_write or system_prepare_write.

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