update_analytics_record

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

Annotations already indicate mutation allowed (readOnlyHint=false) and idempotent. The description adds value by highlighting the dryRun parameter's role in controlling mutation, and clarifies 'add custom tracking properties' which aligns with openWorldHint. No contradictions.

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 two sentences, front-loaded with purpose and a key usage instruction. Every sentence adds value; no wasted words.

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 4 parameters are fully described in the schema, and annotations cover behavioral traits, the description is mostly complete. Missing explicit return value info, but as a mutation tool, that's acceptable.

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 baseline is 3. The description mentions 'dryRun' and 'custom tracking properties' but doesn't add significant new details beyond what the schema already provides.

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 'Updates', the resource 'Cognigy.AI analytics records', and the specific scope 'for a session'. It also explains the purpose 'add custom tracking properties to conversation analytics', distinguishing it from 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?

The description explicitly tells when to use this tool ('add custom tracking properties to conversation analytics') and includes a mutation warning with dryRun usage. It lacks explicit when-not-to-use or alternatives, but the context and sibling list make it clear.

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