kupid_dept_notices

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

With no annotations, the description must disclose behavior beyond what's obvious. It states scraping (read-only) and no authentication needed. However, it does not mention rate limits, error handling, or what happens if a site is unavailable. Adequate but not thorough.

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-organized with a clear purpose statement, then behavior, configuration, and parameter list. It includes an example. Slightly lengthy but essential content is present. Could trim some repetition but overall good.

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 tool involves scraping, dynamic site list, and environment configuration, the description covers key aspects. Output schema exists so return format is likely documented elsewhere. Could mention what the returned list contains (e.g., titles, dates), but still fairly complete.

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 0%, so the description must compensate. It explains each parameter: site_name (empty -> site list), page (default 1), count (default 20). It also describes the environment variable format. Adds significant meaning beyond the schema.

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 queries department/graduate school homepage notices and scrapes the notice board. It distinguishes from the sibling tool kupid_dept_notice_detail by focusing on listing notices rather than details. Mentions returning site list when site_name is empty, adding specificity.

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 notes no authentication required and explains behavior when site_name is empty. It also describes environment variable configuration. However, it does not explicitly state when to use this tool over other notice-fetching siblings like kupid_get_notices, lacking direct alternatives guidance.

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