Purdue University news

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

No annotations are provided, so the description must disclose behavior. It reveals the data source and live API, but does not mention whether repeated calls count against a rate limit, if results are cached, or what happens when the API is unavailable. This is adequate but not comprehensive for a tool with no annotations.

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, well-structured sentence that front-loads the purpose and optionally adds implementation detail in a parenthetical. Every word adds meaning with 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 simple schema (3 optional params, no output schema), the description covers the core behavior (search news, get headlines or full text) and source. It could mention that results are a list of articles or clarify the 'excerpt' default, but for a straightforward read-only tool it is largely sufficient.

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 context by naming the source and the search type ('keyword'), but does not elaborate on the parameters beyond what the schema already documents. No extra value is given for limit or full_text.

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 tool retrieves official Purdue newsroom articles with a specific verb-resource combination. It distinguishes itself by naming the source domain and API backend, and the scope (research announcements, university decisions, campus news) is explicit.

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 explains when to use keyword search ('searchable by keyword') and that omitting the query yields the latest headlines. It does not explicitly contrast with siblings like reddit_purdue or purdue_exponent, but the source (official newsroom) naturally sets it apart.

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