hubspot_get_company

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

The description explicitly labels the tool as 'READ-ONLY', which is a key behavioral trait. No annotations are provided, so the description carries the full burden; it does not mention rate limits, authorization, or error handling, but for a simple get operation, the read-only disclosure is sufficient.

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 extremely concise, with two sentences and a simple list. Every part is necessary and functional; there is no wasted text.

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, an output schema exists (not shown), but the description does not mention error cases (e.g., missing company ID) or default property list behavior. It is adequate but could be more complete for a production environment.

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 description adds a brief 'Args:' section that repeats the parameter names but adds that 'properties' are 'Comma-separated properties to return', which is not in the schema format. However, with 0% schema description coverage, the description provides only minimal additional meaning beyond 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 states 'Get a HubSpot company by ID (READ-ONLY)', which clearly identifies the verb (Get), resource (HubSpot company), and scope (by ID). This distinguishes it from sibling tools like hubspot_search_companies or hubspot_get_contact.

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 you have a HubSpot company ID, but it does not explicitly state when to use this tool versus alternatives like search_companies or get_contact. No exclusions or alternatives are mentioned, though context from sibling tool names provides some inference.

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