get_blog_post

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

There are no annotations, so the description carries the full transparency burden. It discloses that include_content returns the full postBody HTML and warns that it is large, and it clarifies the draft vs live behavior. It does not mention errors, permissions, or read-only guarantees, but 'Fetch' already conveys read-only intent.

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 compact and scannable, with a one-line purpose followed by tight parameter bullets. Every sentence adds useful information, and the most important caveats (large post bodies, draft default) are front-loaded.

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?

For a simple fetch tool with an output schema, the description covers all invocation-relevant details: what to pass, what content to expect, and which version is read. The main gap is the absence of explicit routing guidance against sibling tools, but this is a minor omission given the clear purpose.

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 description coverage is 0%, and the description fully compensates by explaining all three parameters: post_id is the HubSpot blog post ID, include_content controls full postBody HTML with a size warning, and draft distinguishes draft from live versions. This is exactly the semantic value the schema lacks.

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 opens with 'Fetch one blog post,' a specific verb and resource that clearly distinguishes this from siblings like list_blog_posts and get_page. The singular focus and ID-based parameter make its purpose 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?

The description gives useful parameter-level guidance, such as 'leave this off unless you need to edit them' for include_content and explaining draft vs live. However, it never explicitly says when to choose get_blog_post over list_blog_posts or get_page; the selection context is only implied by the word 'one.'

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