get_company_profile

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

No annotations are provided, so the description must carry the full burden of disclosing side effects, auth requirements, etc. It states a read operation (Get) but does not note whether a login session is required, rate limits, or any other behavioral constraints. Given the sibling list includes naukri_login and session tools, the lack of any auth note is a notable gap.

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?

A single, front-loaded sentence that conveys the essential function without fluff. It starts with the verb and resource, and lists the contents concisely. Perfectly sized for its purpose.

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?

The tool has one parameter, no output schema, and no annotations. The description tells what information is fetched (overview, ratings, jobs) but omits any prerequisites such as authentication (inferred from sibling tools), the expected response format, or error handling. Given the simplicity, it is still incomplete without these clarifications.

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 0%, so the description must compensate. It does not explain the parameter beyond the schema's name 'company_slug_or_url'; it never says that this is the company identifier or what format is accepted. The description only mentions the action, not the parameter's role, leaving the agent to infer that the parameter identifies the company.

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 identifies the specific resource (a company's Naukri page) and what it contains (overview, ratings, open jobs). It uses a specific verb 'Get' and is distinct from siblings like search_companies or get_job_details. No ambiguity about the tool's core function.

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 implies usage when one has a specific company identifier, but it does not explicitly contrast with search_companies or state when to use this instead of searching. The context of a single parameter (slug/URL) implies you already have the target, but no explicit when-to-use versus alternatives is given.

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