get_dispatch_settings

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-service profile is covered by structured data. The description adds useful content detail (feature flags, default tip, Drive environment) but says nothing about freshness, caching, or failure behavior when the cloud is unreachable.

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?

One sentence with the key noun phrase front-loaded and a compact parenthetical listing what the settings comprise. No filler, though the parenthetical is slightly list-like and could be tightened.

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 no parameters, annotations covering the safety profile, and no output schema, the description's job is largely to say what comes back, which the parenthetical does at a high level. It stops short of documenting the return shape or auth requirements, but nothing critical for invocation 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?

The tool takes zero parameters, so there is no parameter semantics burden and the schema is trivially complete. Baseline 4 applies; the description correctly makes no attempt to fabricate 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 resource ('Current dispatch settings and feature flags') and the source system (DashPilot Cloud), so an agent knows this is a read of configuration state rather than a delivery action. It is clearly distinguishable from action-oriented siblings like dispatch_delivery or accept_quote, though it does not explicitly contrast itself with get_account or check_drive_connection.

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?

There is no statement of when to call this tool versus alternatives, nor any prerequisite or context such as 'call before dispatch to verify feature flags'. The parenthetical enumerates contents but offers no routing guidance, so usage must be inferred from the name alone.

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