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

No annotations provided. Only behavioral disclosure is that it is free and likely read-only (browse). No mention of pagination, rate limits, or behavior on empty results. Description carries full burden but adds minimal context.

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?

Very concise single sentence, front-loaded with purpose. However, could be slightly more structured (e.g., list parameters) without becoming verbose.

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 3 parameters, no output schema, and no annotations, the description is too brief. Lacks details on return format, sorting, filtering beyond name, or how ranking works. Incomplete for an agent to use effectively.

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 coverage 0% and description does not explain parameters. Implicitly maps q to 'by name', but no details on page or limit. Parameter semantics are entirely missing.

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 clearly states verb (browse/find), resource (profiled companies), and specifics (Fortune 1000 + API providers, ranked by technology-readiness signal). It is distinct from siblings like find_tags or get_company_insight.

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?

No explicit guidance on when to use this tool versus siblings like get_company_insight. Only mentions it's free, but no context on prerequisites or alternatives.

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