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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, but the description adds substantial context: result fields, privacy-offset coordinates, applicant counts, age indicators, and default nationwide behavior. This gives an agent useful operational detail beyond the annotations without contradicting them.

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 front-loaded with the primary use case, then efficiently covers results, filtering, sorting, and default behavior. Despite being a dense paragraph, every sentence contributes relevant information for invoking the tool correctly.

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?

With no output schema, the description appropriately explains the returned fields and link to apply. Combined with complete schema descriptions and annotations covering safety behavior, an agent has enough information to select and invoke this 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 coverage is 100%, so the schema already carries most parameter semantics. The description adds helpful default behavior ('call with no arguments for the most recent open tasks nationwide') and summarizes filter/sort capabilities, though most parameter-level detail remains in the schema.

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 gives a specific verb and resource: browse open jobs posted by homeowners that locals can apply to. The examples ('odd jobs near me', 'yard work jobs in Dallas this week') make the intended resource and audience unambiguous, distinguishing it from sibling tools focused on pricing, worker search, or platform info.

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?

It clearly states when to use the tool via concrete local-user phrasing and explains that filters are optional with a no-argument nationwide default. It does not explicitly name alternatives or when not to use it, so it falls short of a full when/when-not/alternatives rubric.

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