hubspot_get_company

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

No annotations are present, so the description carries the full burden. It fails to disclose behavioral traits such as read-only nature (implied by 'Get'), authentication needs, rate limits, or error scenarios (e.g., what happens if the company ID does not exist). This leaves significant gaps for the AI agent.

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 filler. However, it omits useful details (e.g., optional parameter) that could be included without sacrificing conciseness, so it is not maximally informative.

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 simple retrieval tool with two parameters and no output schema, the description covers the core function but misses the optional properties parameter's existence. It also does not describe the return value structure, which would be helpful given the lack of an output schema.

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 input schema has 100% coverage with descriptions for both 'companyId' and 'properties'. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate. It does not clarify formats, defaults, or interactions between parameters.

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 action ('Get') and the resource ('a company by ID'), distinguishing it from sibling tools that operate on other entity types like contacts or deals. However, it does not mention the optional 'properties' parameter that allows filtering returned fields, which slightly reduces clarity.

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 provides no guidance on when to use this tool versus alternatives like 'hubspot_search_companies' or 'hubspot_list_companies'. It does not specify prerequisites, such as needing a known company ID, nor does it contrast with similar retrieval tools.

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