upsert_blog_summary

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

With no annotations provided, the description carries the full burden and excels: it reveals the upsert logic (no duplicates), mentions the return value (ticket id and created/updated status), warns about exact value requirements for blog_industry, and states that bad data is recorded and reported as failed. This is comprehensive behavioral disclosure beyond what any annotation could provide.

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, every sentence adds critical information, and key points are front-loaded. It covers purpose, safety, return value, parameter constraints, and error handling without redundancy.

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 has 5 parameters, an output schema, and no annotations, the description provides all necessary behavioral context including upsert semantics, exact enum values, and failure behavior. The return value is described, and the output schema structure is implied but not needed in detail. This is complete for an agent to use the tool correctly.

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 must compensate. It explicitly explains the blog_industry parameter's allowed values and failure behavior, and implies the meaning of blog_published_at as the search key. It does not detail subject, blog_summary, or summary_ref_id, but the overall intent is clear enough given the tool's purpose.

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 tool puts a blog post into HubSpot using an upsert strategy, specifies it is the only writer to the blog summary store, and distinguishes itself from siblings by focusing on blog summaries rather than lead profiles. The verb 'put' combined with 'published blog post' and 'upsert' gives a concrete, specific purpose.

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 explicitly states this is for published blog posts and mentions that calling it twice is safe due to upsert behavior. It does not explicitly list when not to use it or name alternatives among siblings, but the sibling tools (upsert_lead_profile, get_lead_profile, get_blog_summary) have different focuses, so the usage context is clear enough.

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