fleetsync_get_drivers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool returns a list and details the fields included, which provides transparency about the output. It does not mention error handling or pagination, but since the tool takes no parameters, a full list retrieval is the expected behavior.

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 two concise sentences that directly communicate the purpose and return content. Every word adds value, with no filler or redundant content.

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 tool with no output schema, the description is complete. It specifies exactly what the returned list contains, and the lack of parameters means no additional context is needed. The tool is simple, and the description fully covers it.

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 has zero parameters and the schema is empty, so there is nothing to add beyond what the schema already shows. The baseline for zero parameters is 4, and the description appropriately avoids inventing non-existent parameters.

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 clearly states the tool's action ('Get all FleetSync drivers') and the specific resource it targets. It also enumerates the returned data fields (names, vehicles, phones, active status), making its purpose unmistakable and distinct from sibling tools that handle routes or orders.

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 implies the tool is for retrieving the full list of drivers, which is a clear usage context. It does not explicitly name alternatives or exclusions, but given that no sibling tool for drivers exists, the intended use is self-evident and requires no further guidance.

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