hubspot_get_property

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns options, validation rules, and metadata, indicating a read operation. However, it does not mention authentication requirements, rate limits, or any side effects. The behavioral disclosure is adequate but not comprehensive.

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, front-loaded sentence of 16 words that clearly conveys the purpose. Every word earns its place; there is no repetition or unnecessary detail.

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 low complexity (2 required parameters, 1 optional), 100% schema coverage, and no output schema, the description is sufficiently complete. It explains the return value content (options, validation, metadata) and the tool's read nature. Slight improvement could include output format hints.

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% description coverage for all 3 parameters. The tool description adds no additional meaning beyond the schema, as the schema already details each parameter. Baseline score of 3 applies.

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 tool retrieves detailed information about a specific property, including options, validation rules, and metadata. This distinguishes it from sibling tools like hubspot_get_properties (which lists all properties) and hubspot_get_property_groups (which retrieves groups), providing a specific verb and resource.

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 for retrieving a single property, but does not explicitly state when to use this tool over alternatives like hubspot_get_properties. No when-not-to-use or exclusion guidance is provided, though the context of sibling tools makes the use case somewhat clear.

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