subject_classifications

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

There are no annotations, so the description carries the full burden. It states the return content ('classification codes, abbreviations, and descriptions') and implies read-only behavior through 'Retrieve.' However, it does not clarify output format, pagination, or any potential restrictions (e.g., whether all classifications are returned by default). The disclosure is adequate but not rich.

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 two sentences, front-loaded with the core purpose and immediately followed by a practical use case. Every word earns its place with no filler or redundancy.

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 lookup tool with six well-documented parameters, the description provides sufficient context: it states what the tool retrieves, why it is useful, and what it returns. There is no output schema, but the description compensates by naming the output fields. It lacks explicit mention of default behavior or result coverage, but the schema's parameter descriptions fill in most 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?

The schema descriptions cover 100% of the six parameters, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already provides, merely echoing 'codes, abbreviations, and descriptions' that correspond to the field options.

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 it retrieves subject area classifications from Scopus or ScienceDirect, a specific verb-resource pairing that distinguishes it from sibling tools like scopus_search or abstract_retrieval. The phrase 'Retrieve subject area classifications' is unambiguous and the tool is dedicated to this lookup.

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 explicitly frames when to use the tool: 'Useful for finding subject codes to filter searches.' This gives clear context for usage without explicitly naming alternatives, but it is distinct enough from siblings that no exclusion is necessary.

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