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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those: it states the tool returns only bookable team members with their locations and services, and that a Cotlet API key with access to this app is required.

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 short and front-loads the purpose, but its first sentence largely restates the second, which also covers the same purpose. The auth requirement and downstream usage are useful, but the opening duplication costs efficiency.

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?

Covers the tool's purpose, required auth, and the fields returned (locations and services), which is sufficient for a simple read-only list tool. It does not mention pagination or whether all team members are returned, but no output schema exists and the complexity is low.

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 coverage is 100%, and the sole parameter location_id is fully documented in the schema as an optional filter defaulting to all locations. The description does not add any meaning beyond that baseline, so a 3 is appropriate.

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 (Lists) and resource (bookable team members), plus the included fields (locations and services). It is clearly distinct from sibling tools like list_appointments or list_services, and the description explicitly connects team_member_id to the appointments workflow.

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?

Explains the downstream use of the result: use team_member_id from an item to filter list_appointments or book with a specific person. This gives clear context for why and when to call the tool, though it does not name explicit alternatives or exclusions.

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