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

The readOnlyHint annotation already establishes this as a safe read. The description adds the 'GET /students' endpoint and, more usefully, enumerates the returned fields (school, grade, subjects, status, billing method, default teachers), which partially compensates for the absence of an output schema. It says nothing about default page size, max per_page, sort order, or how filters combine.

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 front-loaded sentence plus the endpoint reference; there is no filler. Minor redundancy in 'List or search' and the endpoint string echoing the already-annotated read-only nature, but nothing wasteful.

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 13-parameter, zero-required list tool with no output schema, the description gives a reasonable field inventory but omits pagination behavior, default ordering, and any statement that filters are combinable/optional. Adequate but with clear gaps an agent would have to discover from the schema alone.

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 92%, so the schema already documents nearly every filter (page, type, email, grade, school, status, subject, name, customer_id, phone_number, direction). The description adds no format or semantics beyond naming a few of the same fields, so the baseline of 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 or search students') and clarifies the two student kinds it covers (child students of families and independent students). It also enumerates the fields carried in the response, so an agent knows what a student record contains. It stops short of naming any sibling (e.g. teachworks_get_student or teachworks_list_customers) to disambiguate when a single-record lookup is wanted instead.

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?

'List or search' implies the two modes of use (browse vs. filter), and the field list hints at what can be searched on. However, there is no explicit when-to-use guidance, no mention of the sibling teachworks_get_student for single-student retrieval, and no note about paginating through large result sets.

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