tesla_jobs_list

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that Tesla's endpoint always returns the entire dataset, that this tool filters and paginates server-side, and that results contain only metadata. This gives agents accurate expectations about results and performance.

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 four sentences, each conveying necessary information: purpose, endpoint source, upstream behavior, and return limitation. It is front-loaded with 'Tesla Jobs listing' and contains no filler or redundancy, earning every sentence its place.

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 lacking annotations and an output schema, the description adequately explains the tool's scope, return contents (metadata only), and relationship to the job detail endpoint. This covers everything an agent needs to select and invoke the tool appropriately for listing and filtering tasks.

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?

All four parameters are already described in the input schema with 100% coverage. The description mentions filtering and pagination generically but adds no parameter-specific semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 this tool lists and searches Tesla jobs from the public careers site, with the specific verb 'Searches' and a well-defined resource. It distinguishes itself from the job detail tool by noting listings carry metadata only and pointing to the job endpoint for full details.

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 explicitly instructs agents to call the job endpoint for full description/responsibilities when needed, establishing clear when-to-use guidance versus the detail tool. It also explains the search/filter/pagination behavior that is unique to this tool, making it easy to choose it for listing and filtering scenarios.

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