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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no additional behavioral context beyond the list action, such as pagination behavior, auth requirements, or response format. Given the annotations, this is minimally adequate.

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 a single concise sentence that directly states the tool's purpose with no filler. It is front-loaded and efficient, earning perfect marks for conciseness.

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?

The tool has 5 undocumented parameters and no output schema. The description only states 'list gym employees/staff' and does not explain filtering options, pagination, or the return structure. This leaves the tool incomplete for practical use, as the agent cannot safely invoke it with meaningful filters or interpret results.

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 schema includes 5 optional parameters (name, skip, take, email, account) with 0% description coverage. The description provides no explanation of these parameters, leaving the agent unable to understand their purpose, format, or how to use them for filtering. This is a critical gap for a tool with multiple 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 it lists gym employees/staff, using 'list' as a specific verb and 'gym employees/staff' as the resource. This distinguishes it from sibling tools like evo_member_list (members) and evo_prospect (prospects).

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?

No usage guidance is provided. The description does not mention when to use this tool vs alternatives, nor does it state exclusions or prerequisites. The agent must infer usage from the tool name and sibling context.

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