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

No annotations are provided, and the description gives no behavioral details: no indication of read-only vs. side effects, no auth or rate-limit notes, no return behavior. The description carries the full burden and completely fails to disclose anything beyond a static label.

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 extremely short, but this is under-specification rather than effective conciseness. A single three-word phrase provides no structure or front-loaded information. It is not concise in a meaningful way; it simply omits all necessary content.

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 tool with 4 parameters, no output schema, no annotations, and ambiguous sibling relationships, the description is completely inadequate. An agent cannot correctly invoke or select this tool based solely on this definition.

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 no parameter descriptions exist in the schema or the tool description. The four parameters (query, country, language, maxTimeout) have names only, with no explanation of format, defaults, or expected values. The description adds zero semantic value.

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 'V1 Jobs Linkedin' only restates the tool name and suggests a domain (LinkedIn jobs), but does not specify a verb or action. It fails to distinguish the tool from siblings like jobs_indeed or jobs_multi, leaving the agent to infer the actual purpose from the tool name alone.

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 whatsoever about when to use this tool instead of alternatives. The sibling tools (jobs, jobs_indeed, jobs_multi) are not mentioned, and no context or condition is provided, so the agent has no basis for tool selection.

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