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

Annotations only declare readOnlyHint=true; the description adds a genuinely useful auth behavior not in structured data: 'Without a staff token only public fields return.' It also cites the underlying endpoint (GET /staff/staff). It does not describe pagination or rate limits, but the auth caveat is meaningful added context.

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?

Three tight sentences with no filler: identity/scope first, the two filtering modes second, the auth caveat and endpoint last. Every sentence carries load and the key constraint is front-loaded.

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 7-parameter, zero-required read tool with no output schema, the description covers the main query modes and one important behavioral caveat. Return-field detail is arguably needed since no output schema exists, but the annotations plus schema cover most of what an agent needs to call it correctly.

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?

Schema description coverage is 100%, so every parameter is already documented, including the session_type_id/location_id/start_date_time co-dependency. The description restates that dependency rather than adding syntax or constraint detail, so baseline 3 applies.

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?

States a specific verb+resource ('List staff members') and clarifies the domain meaning with '(instructors, practitioners)', so an agent knows what a staff record is. It does not explicitly distinguish itself from the closest sibling, mindbody_list_staff_appointments, but the resource is unambiguous.

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?

Gives concrete usage conditions: filter by role, or use the availability pattern with session_type_id + location_id + start_date_time together. It does not name alternative tools or state when not to use this one, so it stops short of a 5.

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