search_jobs

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

With no annotations, the description carries full burden. It only states 'search' with no disclosure of return format, pagination behavior, authentication needs, or rate limits. This is a significant gap for a search tool.

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 single-sentence description is concise but under-specified. It is not front-loaded with critical details; the brevity sacrifices utility. An adequate length for a minimal description but lacks substance.

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 two parameters, no output schema, and 22 sibling tools, the description is insufficient. It does not explain return values, pagination, or how 'q' filters results, leaving the agent with too many unknowns for reliable use.

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 50% (q described, page not). The description adds no meaning beyond the schema; it does not clarify how to use 'q' (e.g., fields searched) or 'page' (e.g., starting from 1? 0?). Fails to compensate for the missing schema descriptions.

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 'Search open gun.io job listings' clearly identifies the verb (search) and resource (job listings), and distinguishes this tool from siblings like get_job (single job) or list_applications (applications) by focusing on searching open listings.

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?

No guidance on when to use this tool versus alternatives (e.g., get_job, list_interviews). No mention of prerequisites or typical scenarios, leaving the agent to infer usage from the name alone.

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