Search jobs

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

With no annotations provided, the description carries the burden of disclosure. It goes beyond a vague 'search' by specifying case-insensitivity, substring matching, and the exact columns considered, which is meaningful behavioral context. It omits return format or pagination, but core matching behavior is transparent.

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, front-loaded sentence with no filler. It precisely conveys the tool's behavior in minimal words.

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 one-parameter search tool with no output schema, the description is adequately complete. It covers the search scope and matching behavior, though it could optionally mention what the return payload looks like. Overall, the tool is simple enough that this description suffices.

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 fully describes the single parameter with 100% coverage, so the baseline is 3. The description adds semantic value by explaining how the query is used (case-insensitive substring across Company, Position, Notes), which helps the agent understand the query's effect beyond the schema's generic 'Keyword or phrase to search for.'

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 performs a case-insensitive substring search across specific columns (Company, Position, Notes). This is a specific verb+resource+scope that distinguishes it from sibling tools like list_jobs or get_job.

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 implies the use case: when you need to find jobs by a keyword across three textual fields. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to decide when to invoke this tool.

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