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

With no annotations, the description must carry the full burden of disclosing behavior. It mentions the core functionality but omits key behaviors like pagination (page parameter), the return structure, and the worldwide-overrides-country interaction (though that is in the schema, the description adds nothing beyond it). For a list tool, this is insufficient behavioral disclosure.

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 a single, concise sentence with no fluff. It front-loads the main purpose ('Browse remote-friendly companies') and mentions filters efficiently. There is no wasted wording.

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 tool with no output schema and a sibling 'search_companies', the description should hint at what the response looks like and when to use this over other search/list tools. It provides none of that, leaving the agent to guess about pagination, return format, and differentiation. The description is too sparse to be fully actionable.

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 the baseline is 3. The description only restates the existence of filters ('country or worldwide availability') without adding any new semantics or usage nuances beyond what the schema already documents. It does not compensate for any gaps, but none exist in 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 browses remote-friendly companies with optional filters, which is a specific verb and resource. It does not explicitly differentiate from the sibling 'search_companies', so it lacks that distinguishing clarity that would earn a 5.

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 guidance on when to use this tool versus 'search_companies' or other listing tools. The description only states what it does, not when it is the preferred choice, and no exclusions or alternatives are mentioned.

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