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

readOnlyHint=true already tells the agent this is a safe read. The description adds that results are scoped to 'the business's' instructors and enumerates returned fields, which is useful context, but says nothing about pagination defaults, result caps, or ordering.

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?

Two short, front-loaded sentences with the verb and resource first and scope/returned fields second. The trailing 'TeamUp: GET /instructors' is traceability rather than instruction, but its cost is minimal.

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?

A five-parameter, zero-required read tool with fully described schema and no output schema. The description compensates for the missing output schema by naming the returned fields (name, bio, staff id), leaving little an agent needs before invoking 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?

Schema description coverage is 100%, so page, page_size, query, expand and fields are each documented in the schema. The description adds no parameter-level meaning beyond the field list it advertises, so the 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 and resource ('List the business's instructors') and clarifies the domain synonyms (coaches, trainers), so an agent knows what entity is returned. It does not explicitly differentiate itself from the many other goteamup_list_* siblings, but the resource noun 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?

Usage is only implied: this is the tool for enumerating instructors, with no explicit when-to-use, prerequisites, or pointer to an alternative. For a straightforward read-only list endpoint the implied usage is probably sufficient, but no routing guidance is offered.

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