find_matching_linkedin_jobs

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

With no annotations provided, the description must disclose behavior. It only vaguely hints at 'local matching' and 'public LinkedIn job data', but does not explain whether this is a read-only operation, whether it makes network calls, what side effects exist, or any required authorization. This is severely insufficient.

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 short sentence, so it is concise in length, but it is under-specified to the point of being unhelpful. It does not front-load any concrete information beyond a vague action and resource.

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?

Despite having an output schema and five parameters, the description lacks almost any context about the tool's behavior, configuration requirements, or relationship to siblings. It is completely inadequate for an agent to select and invoke the tool correctly.

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 0%, and the description mentions none of the five parameters. It does not explain how 'location', 'max_jobs', 'date_posted', 'max_queries', or 'limit_per_query' affect the matching behavior. The description adds no meaningful parameter information.

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 uses a vague verb 'Run' and an unclear resource 'configured local matching over public LinkedIn job data'. It does not clearly state what the tool actually does (e.g., finds matching jobs, returns a list of matches) nor how it differs from sibling tools like search_linkedin_jobs.

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?

There is no guidance on when to use this tool versus the sibling tools. It does not mention any prerequisites, configuration steps, or situations where this tool is preferred.

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