hubspot_get_deal

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

The description labels the tool as 'READ-ONLY', which is a behavioral trait, but lacks details on authentication, rate limits, error behavior (e.g., if deal not found), or response structure. Since no annotations are provided, the description carries the full burden and falls short.

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 concise with a clear docstring format including Args. It front-loads the purpose and is efficient, though it could be slightly more detailed without being verbose.

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 tool has a simple purpose (get deal by ID) with an output schema available, so the description adequately covers the core functionality and parameter usage. Missing notes on error conditions or rate limits, but still reasonably complete for a basic retrieval 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?

The schema has 0% description coverage, so the description's parameter explanations add value. It defines deal_id as 'HubSpot deal ID' and properties as 'Comma-separated properties to return', which clarifies usage beyond the schema titles. Could be improved by listing valid properties or referencing the defaults.

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?

Clearly states 'Get a HubSpot deal by ID (READ-ONLY)' with a specific verb and resource. Distinguishes from siblings like hubspot_search_deals or hubspot_get_contact by focusing on getting a single deal by ID.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., search deals, get deal associations). The description only states the action without contextual usage advice.

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