search_subjects

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

There are no annotations, so the description carries the behavioral transparency burden. It clearly implies a non-mutating browse/search operation and reveals the key outcome (subject IDs), but it does not describe the return format, pagination, or any side effects beyond what the schema already covers.

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?

Two concise sentences, front-loaded with the action and resource, followed by the practical purpose. No filler or repetition; every phrase 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 search tool with no output schema and all parameters optional, the description covers purpose and workflow integration. It stops short of describing the response shape, but 'discover subject IDs' implies the essential return value.

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. The description adds strategic context rather than parameter-level details, and the schema already explains name filtering, limit, and parent_id sufficiently.

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 uses a specific verb ('Browse or search') and names a concrete resource ('GUS BDL subject categories') with concrete examples. It also states the downstream purpose ('discover subject IDs which then anchor variable searches'), distinguishing it from sibling tools like search_variables and search_units.

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 gives clear context for when to use the tool: to discover subject IDs that lead into variable searches. It does not explicitly name alternatives or state when not to use it, but the intended workflow placement is clear enough for an agent.

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