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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the authentication requirement, which is a key behavioral trait, but it omits other important details such as what the tool returns, how it handles unauthenticated calls, or any potential side effects. For a tool that could be confused with get_company_details, this is insufficient.

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—two short sentences with no filler. It front-loads the primary purpose ('Get your company's profile') and follows with the authentication requirement. This is well-structured and efficient, though it is arguably too minimal for the complexity of the tool ecosystem.

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?

Given the tool's simplicity (0 params, no output schema), the description covers the basics but leaves ambiguity about its scope relative to sibling tools. It does not explicitly clarify that this is specifically for the authenticated employer's own company, nor does it explain the return format. The description is not misleading but is incomplete for confident tool selection.

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?

The tool has zero parameters, so the schema trivially covers everything. The description adds no parameter information because none is needed. Baseline for 0 parameters is 4, and the description meets that standard without adding unnecessary details.

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 it retrieves 'your company's profile on Himalayas,' indicating a specific resource (company profile) and context (the caller's own company). It distinguishes implicitly from get_companies (a listing) and get_company_details (likely any company) via the 'your company' phrasing, but it does not name these siblings explicitly.

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?

It mentions the precondition of employer authentication but provides no guidance on when to choose this tool over get_company_details or similar tools. No alternatives are named, and no conditions for when to use it versus others are given. The agent is left to infer the appropriate use case from the tool name alone.

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