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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the listing is public, unfiltered, lightweight, and contains only name, description, and website fields, giving the agent a clearer picture of what to expect.

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 concise and front-loaded, with every clause earning its place. The core purpose comes first, and the clarifying parenthetical about being a lightweight listing, not a job-posting system, prevents misinterpretation without bloat.

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 simple read-only listing with two optional pagination parameters, the description covers purpose, access (public), filters (none), and item composition (name, description, website). There is no output schema, so a bit more detail about the response envelope would be nice, but it is not a critical gap for such a lightweight tool.

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 100%, so page and page_size are already fully documented. The description adds the useful context that there are no filters, which explains why only pagination parameters exist, but it does not add significant parameter-level detail beyond 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 clearly states the tool lists companies not yet on ClusterHack, using a specific verb and resource. It also explicitly distinguishes itself from a job-posting system, resolving confusion raised by the tool name 'vacancies' and differentiating it from company_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 description gives clear context: use this for the public, unfiltered board of off-platform companies. It also states what it is not ('not a job-posting system'), which helps an agent avoid misuse, though it does not explicitly name alternatives like company_list.

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