search_professors

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

No annotations are provided, so the description carries full responsibility. The description does not disclose behavioral traits such as side effects, permissions, rate limits, or error conditions. It only describes parameters and return shape, leaving the agent uninformed about operational behavior.

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 well-structured with clear Args and Returns sections, and the main purpose is front-loaded. While it is longer than necessary, every sentence provides useful information, and there is no 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?

Given the high parameter count and no output schema, the description covers all parameters and the return shape. It references a sibling tool for further detail. However, missing behavioral transparency and explicit usage guidelines prevent a higher score.

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 0%, and the description compensates thoroughly. Each parameter is explained with meaningful context (e.g., 'topic_keywords: Core topic terms (high scoring weight)', 'regions: Country/region codes. Supported: US, UK/GB, JP...'). This adds substantial value beyond the schema titles.

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 'Search for professors matching research interests (coarse filter).' This provides a specific verb ('search'), resource ('professors'), and a qualifying scope ('coarse filter'), effectively distinguishing it from the sibling 'find_professors' tool.

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 hints at an alternative tool by referencing 'See find_professors' for topic_keywords, and the phrase 'coarse filter' suggests this is for broader queries. However, it does not explicitly state when to use this tool versus find_professors or provide when-not-to-use guidance.

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