get_classes

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

readOnlyHint=true already declares this as a safe read, so the description's burden is lower. It adds the word 'all', implying no pagination or partial results, which is useful. It does not mention the 'raw' flag's effect, output shape, or error behavior for invalid standard/version combinations.

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?

Three short sentences, front-loaded with the purpose, then examples of return values, then a usage example. Nothing is padded, though the example line duplicates information already in the schema descriptions.

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 full schema coverage and no output schema, the description is largely sufficient: it states the input concept and gives a sample of what the class list contains. Minor gaps remain around where this fits in the larger standard/class/dataset hierarchy.

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%, so all three parameters are already documented, including the raw flag and the 'latest' version value. The description's only added value is a concrete example pairing ('sdtmig', '3-4'), which confirms the two required parameters must be used together but adds no new semantics. 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?

The description states a specific verb and resource: retrieve the list of all classes contained in a given standard, and names concrete class examples (Events, Findings, Interventions, SpecialPurpose). This is distinguishable from siblings like get_datasets or get_datastructures, though the description never explicitly contrasts itself with them.

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 implied by the example invocation (standard='sdtmig', version='3-4'), which shows the tool is the entry point for enumerating classes. However, there is no explicit when-to-use/when-not guidance and no mention of how this differs from get_datastructures or get_datastructure_varsets in the workflow.

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