hubspot_describe_object

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly says 'READ-ONLY', which is important, but it does not mention anything else about behavior, such as errors for invalid object names, pagination, or response structure. The disclosure is correct but minimal.

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 one compact sentence, front-loaded with the action and resource, and ends with the clearly marked 'READ-ONLY' note. Every word contributes value with no redundancy.

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 straightforward introspection tool with two fully documented parameters, the description covers the essential context: what it lists and why an agent would use it. The lack of an output schema and explicit return format is a minor gap given the tool's simplicity and low risk.

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 100%, so the parameters are already fully documented in the input schema. The description does not add parameter-level meaning beyond the schema, which is acceptable but does not earn a higher score.

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 a specific verb ('List') and the resource ('properties/fields of a CRM object type'), and explains the purpose: to know what to search on and what to request. This clearly distinguishes it from sibling tools like hubspot_list_objects, which list object types themselves.

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 phrase 'so you know what to search on and what to request' conveys when to use this tool: before constructing searches or get requests. The object parameter also directs users to hubspot_list_objects for discovering custom object types, adding useful cross-tool guidance. It does not explicitly say when not to use it, but the intended context is clear.

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