hubspot_update_note

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the update is partial or full replacement, required permissions, or side effects. The description 'Update a note's content or properties' is too brief to convey behavioral details.

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 with no wasted words. It is concise, but could be restructured to include more key information without adding length. The brevity is acceptable, but there is room to front-load more useful details.

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 no output schema and no annotations, the description should provide more context about return values or behavioral effects. It does not explain what the response looks like (e.g., updated note object or success message). For a mutation tool, this is insufficient completeness.

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 100% coverage with descriptions for all four parameters. The description adds minimal meaning beyond the schema, as it only mentions 'content or properties' without elaborating on the parameters. With high schema coverage, a score of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 verb 'Update' and the resource 'note', and specifies that it can update 'content or properties'. It distinguishes from sibling tools like hubspot_get_note or hubspot_delete_note, but could be more specific about what 'properties' include in contrast to other update tools.

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 guidance is provided on when to use this tool vs alternatives like hubspot_update_contact or hubspot_update_deal. There is no mention of prerequisites, restrictions, or when not to use this tool. The description lacks any usage context.

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