hubspot_crm_get

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

Without annotations, description reveals key behaviors: returns 404 if missing or archived, properties parameter required for custom fields, archived parameter toggles record type. Good coverage but does not explicitly state read-only nature.

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?

Two sentences plus an emphasized note. Front-loaded with purpose, then key usage tips. No extraneous information. Efficient and clear.

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?

Covers purpose, all object types, required parameters, important optional parameter, error handling. Lacks response format description and usage of `associations` but overall adequate for a simple get tool with no 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?

Schema coverage is 100%, baseline 3. Description adds value by emphasizing `properties` with example and explaining default behavior. Also clarifies `archived` and 404 implications. Does not add much for `associations` but overall enhances understanding.

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?

Explicitly states 'Retrieve a single HubSpot CRM record by its ID' and 'Works with all object types'. Clearly distinguishes from sibling tools like list, search, and batch read by specifying single record retrieval.

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?

Provides important guidance: always specify `properties` for non-default values and use `archived=true` for archived records. Mentions 404 error behavior. Does not explicitly compare to alternatives but context is clear.

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