hubspot_log_activity

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

No annotations provided, so the description carries full burden. It states 'Log' which implies a write operation, but does not disclose any side effects, permissions required, or limitations. The description is minimal and adds little beyond the parameter schema.

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 a single sentence of 12 words, efficiently stating the purpose. It is front-loaded and contains no unnecessary information. Could be improved by adding brief usage context, but it is appropriately sized for a simple tool.

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 tool with 3 parameters all described and no output schema, the description is minimal. It does not explain what the tool returns, error conditions, or caveats. While sufficient for basic understanding, it lacks completeness for complex use cases.

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 100%, so the schema already explains each parameter. The description adds no extra meaning beyond listing activity types. Baseline score of 3 is appropriate as the description does not harm but adds negligible value.

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 logs an engagement (note, email, or call) on a contact's HubSpot timeline. It uses a specific verb 'Log' and identifies the resource. However, it does not differentiate from sibling tools, but siblings are distinct in function.

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. The context implies it should be used to log activities on contacts, but lacks exclusions or conditions. Sibling tools are different enough that confusion is unlikely, but guidance would improve usability.

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