IndividualClassesGetList

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

The annotations already communicate that this is read-only and non-destructive. The description adds minimal behavioral context beyond the list operation itself, and does not explain open-world behavior, response shape, or pagination semantics. It is consistent with the annotations but adds little beyond them.

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 concise sentence with no filler. It front-loads the action and resource, and every word contributes to the meaning.

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 all optional parameters, the description plus schema and annotations is largely sufficient. The lack of an output schema means a brief note on what fields are returned would have improved completeness, but it is not critical for basic invocation.

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?

The input schema has 100% description coverage for all six optional parameters, so the structural burden is already satisfied. The description only adds the high-level notion of 'filters and pagination' without detailing any individual parameter semantics.

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 clearly states the verb 'List' and the resource 'individual classes', and adds 'optional filters and pagination' to define the operation's scope. It is clear enough to distinguish from IndividualClassesGetDetail, though it does not explicitly name the sibling alternatives.

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 description implies this tool is for listing individual classes with optional filters and pagination, but it gives no explicit guidance on when to prefer this over related tools like IndividualClassesGetDetail or AccessGroupsGetIndividualClasses. The usage context is present but left implicit.

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