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

Annotations already mark readOnlyHint and idempotentHint, and the description adds meaningful behavioral detail beyond them: it never consumes plan stops, and it explains the empty=true and plan_missing=true flags, including the consequence that a plan_missing automation cannot run until fixed in the dashboard.

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?

The description is dense but every clause earns its place: it front-loads the core purpose, lists the salient fields in a compact enumeration, and ends with the two important output flags. It is thorough without becoming padded or redundant.

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?

Given zero parameters, rich annotations, and an output schema, the description fully covers what an agent needs: the scope (account), the no-argument nature, read-only status, plan-stop cost, and the meaning of special output states. Nothing essential is missing.

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?

With zero parameters and schema coverage at 100%, the description still adds value by explaining that the tool implicitly answers for the account the credential belongs to. No parameter documentation is needed beyond this, and the schema already states 'No arguments'.

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-resource pair ('List the connected Vepathos account's standing rules') and enumerates the exact details returned, making it clearly distinct from siblings like list_plans or list_fleet. It also notes it returns connected stores, tying it to create_automation's input without confusing it with account-level tools.

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 description clearly states this tool takes no arguments, is read-only, and does not consume plan stops, which guides safe usage. It does not explicitly say when to prefer this over alternatives like list_plans, but the focused resource and sibling context make the intended use clear.

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