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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by declaring the endpoint public (no auth barrier) and indicating that responses include company ids plus the listed fields. No contradiction with annotations.

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 concise sentences: the first front-loads the resource and returned fields, the second gives the key usage instruction. Every word earns its place, with no redundant or vague filler.

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 two-parameter read-only list endpoint with no output schema, the description sufficiently explains what is returned and why to call it (finding company ids). It does not cover edge cases such as empty results or ordering, but those are minor given the straightforward pagination schema and annotations.

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%, with page and page_size fully documented in the input schema. The description does not add parameter-level details, but the baseline of 3 applies because the schema already carries the parameter meaning.

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?

Description identifies the resource ('ClusterHack company pages') with a concrete verb ('Browse'), enumerates returned fields (name, description, org type, website, logo), and clearly states its role as the id-lookup precursor to other company tools. This distinguishes it from siblings like company_get without needing to open any schemas.

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?

Provides clear context: it is public data and should be used to find a company's id before calling any other company tool. This tells the agent when to use it, though it does not explicitly name alternative tools or state exclusion cases.

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