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

Annotations already supply readOnlyHint and openWorldHint; the description adds a genuinely useful behavioral fact beyond them by disclosing that the endpoint is 'anonymous', i.e. no authentication is required. It does not discuss pagination or the results_per_page behavior, so it is helpful but not complete.

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?

A single dense, front-loaded sentence that names the tool first and then the filters and data source; no filler. It is efficient, though the compressed filter list is doing a lot of work in one clause.

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 7-parameter read-only search with an output schema, the description needn't explain returns, but it leaves sorting, pagination, and remote filtering unexplained and gives no usage context. Adequate but with clear gaps.

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%, so the description must carry parameter meaning. It names team/location/keyword filters that map to teams/offices/q, but omits sort_by_new, results_per_page, and remote filtering, and 'employment-type' has no obvious matching property, so compensation is only partial.

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?

States a specific verb and resource ('Meta Jobs search') and the filter dimensions covered, plus the underlying data source (metacareers.com's jobsearch GraphQL). It is immediately distinguishable from a detail or list tool, though it does not explicitly name its siblings meta_jobs_job / meta_jobs_list.

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 filter list implies the tool's use case (searching jobs by team/tech/location/type/keyword), but there is no explicit when-to-use guidance, no conditions, and no routing to the sibling job-detail or list tools. Usage is left to inference.

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