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

With no annotations, the description carries the burden of behavioral disclosure. 'List' clearly signals a read-only operation, and the description adds specific output semantics by enumerating liveness values (live | stale | offline). It does not mention pagination, performance, or error behavior, but for a zero-parameter list tool these omissions are minor.

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?

A single, tightly written sentence that leads with the action and resource, then specifies the return fields and value domain. No wasted words.

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 parameterless read-only list tool with no output schema, the description adequately explains what the agent will receive: kind, capabilities, and liveness with explicit status values. It could mention whether the lane list is filtered or ordered, but nothing critical is missing for selecting and invoking the tool.

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 schema description coverage is 100%, so the schema fully covers the input surface. There is nothing for the description to add about parameters, and none are needed.

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 a specific verb, 'List,' and a specific resource, 'FLOCORE mesh lanes,' along with the exact fields returned (kind, capabilities, liveness). This distinguishes it from sibling tools like flocore_list_tenants and flocore_list_tickets without needing to open schemas.

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 tool's purpose is self-evident from the name and description, so when to use it is reasonably implied. However, there is no explicit guidance about when it should be preferred over sibling tools, nor any exclusions or contextual notes about mesh lane inspection.

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