hubspot_get_properties

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

No annotations are provided, so the description must fully disclose behavior. It correctly indicates a read operation ('Get all available properties'), but it lacks details on authentication requirements, error handling for invalid objectType, or response structure. Additional context would benefit the 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 consists of two concise sentences, front-loads the core action ('Get all available properties'), and provides practical use context without extraneous words.

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, good schema coverage, and lack of output schema, the description sufficiently conveys the tool's purpose and value. It could optionally mention what properties are returned (e.g., name, type), but this is not critical for a straightforward discovery tool.

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?

Both parameters have descriptions in the input schema (100% schema_description_coverage). The description does not add extra semantic information beyond the schema, so the baseline score of 3 is appropriate.

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 verb 'Get', the resource 'properties for a HubSpot object type', and the purpose 'discover what fields can be used when creating, updating, or searching objects'. It effectively distinguishes this tool from sibling tools like hubspot_get_property (singular) and CRUD operations.

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 implicitly guides usage by stating the tool is for discovering fields before creating/updating/searching. Although it does not explicitly mention when not to use or alternatives, the sibling tool list includes hubspot_get_property for single property retrieval, providing clear differentiation.

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