hubspot_get_meeting

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

No annotations are provided, and the description only states 'Get a specific meeting engagement by its ID.' It does not disclose any behavioral traits such as error handling (e.g., what happens if the ID is invalid), required permissions, or whether the operation is read-only. For a tool with no annotations, the description should provide more behavioral context.

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?

A single sentence that conveys the essential purpose without any superfluous words. It is efficiently structured.

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 absence of an output schema, the description does not explain what data is returned. However, for a simple retrieval operation with well-documented parameters, the description is minimally adequate. It lacks details about response format or possible incomplete results.

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 are documented in the input schema with descriptions (100% coverage). The description adds no additional meaning beyond 'by its ID' which is already captured by the required meetingId parameter. The baseline score for high schema coverage 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 action ('Get') and the resource ('a specific meeting engagement by its ID'). The verb and resource are specific, and the tool name reinforces the domain. While it doesn't explicitly differentiate from sibling tools, the resource type is unambiguous.

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 like hubspot_search_meetings or hubspot_list_meetings. However, the purpose ('get by ID') implies it is for retrieving a single known meeting, which is a common use case. Lack of exclusions or context makes it minimally acceptable.

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