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

Annotation readOnlyHint=true is consistent with the tool being a read-only rules fetch. The description adds real behavioral context beyond the annotation: mandatory invocation ordering and the failure mode for non-compliance.

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-loads the MANDATORY FIRST STEP directive and stays to three sentences. The final sentence restates the mandate already implied earlier, a slight redundancy, but the overall shape is 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?

For a zero-parameter, no-output-schema gate tool, the essential information (call first, what it returns, why it matters) is present. It does not describe the form of the returned rules, which is a minor gap given there is nothing to configure.

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?

The tool takes zero parameters, so the baseline is 4. Nothing in the description is needed to disambiguate arguments, and there are none to mis-specify.

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 action (unlock) and what it yields (the operating rules and constraints governing all other Shareflo tools). Its role as a mandatory prerequisite clearly distinguishes it from the CRUD siblings, though the nature of the returned 'rules' remains abstract.

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 states when to call it (once at the start of every conversation, before any other Shareflo tool) and the consequence of skipping it (other tools produce incorrect or rejected results). No inference required.

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