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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: results are paginated one page at a time and include vendor totals. It says nothing about page-size limits, ordering defaults, or error behavior.

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?

Two short sentences with the core scope front-loaded, followed by the pagination caveat. The raw endpoint path is of marginal value to an agent but is compact and not distracting.

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 5 undocumented parameters, no output schema, and a paginated result set, the description should explain ordering, page size, and how 'vendor totals' are shaped in the response. It mentions only paging in passing, leaving most calling decisions to guesswork from bare schema constraints.

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% across 5 parameters, so the description carries the full burden and largely fails it. 'Page' and 'subsequent pages' hints at pagination, but rows, sort_by, sort_direction and even project_id are never explained; the enums and min/max ranges in the schema have no narrative counterpart.

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 ('List a single page of the jobs in a project') plus what the payload includes ('with vendor totals'). An agent can distinguish it from hirehop_get_job (one job) and hirehop_search_jobs (cross-project search), though neither sibling is named.

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?

'Use subsequent pages for the full project' tells the agent this is one page of a larger set, which is useful. But there is no explicit when-to-use vs hirehop_get_project or hirehop_search_jobs, and no preconditions or exclusions.

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