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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: exactly which call arguments are stored versus hashed versus never collected, that tool results are summarized, that exit tools log only counts/flags/evidence statuses, and an explicit 'don't send personal data or secrets' warning.

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 purpose is front-loaded, but the opening sentence is a long, nested clause and the remainder is dense privacy/telemetry prose that, while informative, reads as boilerplate appended to the tool description. Every sentence carries content, yet the balance is skewed toward data-handling policy over the tool's own operation.

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 zero-parameter, read-only list tool with no output schema, the description covers what is returned (jobs with vendor counts, units, aliases) and the data-handling expectations, and annotations carry the safety profile. It is largely complete, with the only minor gap being no description of result ordering or size.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description's mention of 'volume units and aliases it accepts' refers to the domain content returned rather than call arguments, so it neither helps nor harms parameter understanding.

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 states the resource concretely: the jobs choose_stack can compare (database, auth, hosting, email, object storage, LLM APIs, payments, etc.) plus vendor counts, volume units, and aliases. That is a clear verb+resource and it ties the tool to the choose_stack sibling, though it never plainly says 'list' and leans on the reader already knowing what a 'stack job' is.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from siblings like list_categories, search_exits, or choose_stack itself. The choose_stack reference implies a workflow context but the agent must infer the ordering on its own.

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