AccessGroupsGetTeachers

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is established. The description adds the useful pagination trait, which is not present in the annotations. It does not go further to describe response shape, default page size, or any additional behavioral constraints, but the annotation coverage lowers the burden.

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, front-loaded sentence with no filler. It states the core operation and the key pagination trait efficiently. Every word earns its place.

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 simple read-only list tool with only three scalar parameters and supporting annotations, the description is nearly sufficient. It identifies the resource, the grouping criterion, and pagination. It does not describe the returned teacher fields, but given the simplicity and the schema, an agent can invoke the tool correctly without major gaps.

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 the baseline is 3 even though the property descriptions are largely tautological ('integer (optional)'). The tool description itself adds no parameter-level meaning beyond 'paginated', which weakly maps to Skip and Take. The required accessGroupId is not explained in the description but is visible in the schema.

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 states a specific verb and resource: 'List teachers assigned to an access group'. This clearly conveys what the tool does and broadly separates it from sibling tools that list group classes, individual classes, or access groups themselves. However, it does not explicitly name or contrast sibling alternatives, so it stops short of full differentiation.

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?

The intended use is implied: when a caller wants the teachers assigned to a particular access group. There is no explicit guidance about when to use this tool instead of related tools like AccessGroupsGetDetails or AccessGroupsGetGroupClasses. The absence of exclusions or named alternatives leaves the routing mostly to inference.

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