hubspot_properties_get

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

The description discloses the tool's read-only behavior by stating it 'retrieves' data, but lacks explicit mention of error handling (e.g., if the property does not exist) or potential rate limits. Since no annotations are provided, the description carries full burden for behavioral transparency, yet it only minimally covers it.

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 brief (two sentences) and front-loaded with the core action and purpose. Every sentence provides essential information without unnecessary words, making it highly efficient.

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 description adequately explains what the tool returns given no output schema, covering key details of the property definition. It does not mention edge cases like missing properties or pagination (not relevant), but for a simple retrieval tool, it is sufficiently complete.

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 coverage is 100% with clear descriptions for both parameters. The description adds value by explaining that propertyName is the internal name and that the returned object includes type, field type, group, options, and default/custom status, which goes beyond the schema's parameter descriptions.

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 specifies retrieving the full definition of a specific HubSpot CRM property by its internal name, including details like type, field type, group, options, and whether it's a HubSpot default or custom property. It effectively distinguishes this tool from siblings like hubspot_properties_list (which lists all properties) and hubspot_crm_get (which gets a record value).

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 advises that the tool is 'useful for inspecting field constraints before creating or updating records,' providing implicit guidance on when to use it. However, it does not explicitly state when not to use it or name alternative tools for different purposes, leaving room for clearer differentiation.

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