find_board

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

Annotations already declare this is a read-only, idempotent, open-world lookup, and the description adds substantial behavioral context: guessed names can belong to another company, sample titles should be checked, and several provider families require a job link rather than a name. These matching quirks go well beyond the annotations without contradicting them.

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 long, but the density is justified by the many provider-specific lookup rules and examples. It is front-loaded with the core purpose and caution, though the provider details could be more scannable if structured as bullets.

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?

With an output schema present, the description need not explain return values, and it covers the complex matching behaviors an agent needs before calling the tool. The annotations and schema are supplemented rather than repeated.

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 documents the single company parameter at 100% coverage, but the description adds meaningful accepted forms and provider-specific syntax, such as avature:host/portal/careers, icims:<company>, jobvite:<company>, and hn:whoishiring. It tells the agent when a company name will work and when a link is required.

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 states a specific verb and resource: find a company's job board by name or job/careers link, and says it returns watchlist entries. It also distinguishes this lookup from add_board and add_application, so an agent can route correctly among siblings.

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?

It explicitly says to use this before add_board, and to use add_application instead when tracking one job from its link. It further gives concrete when-to-use-link guidance for Workday, Oracle Recruiting Cloud, Jibe, Avature, iCIMS, and Jobvite boards.

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