update_tracker

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

Despite no annotations, the description discloses critical side effects: updating destination_number updates the call_flow's destination, and greeting_text requires destination_number to avoid breaking the tracker. Field-level rules (non-empty strings, pass None to leave unchanged) are detailed.

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 well-structured with sections (Args, Field-level rules) and front-loaded with purpose. It is slightly verbose but each sentence adds necessary context. Could be tightened slightly, but still highly effective.

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 complexity (7 parameters, one required) and presence of an output schema, the description covers all essential behavior, side effects, dependencies, error avoidance, and field constraints. It is complete enough for safe and correct invocation.

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?

With 0% schema coverage, the description fully compensates by explaining each parameter's meaning, default behavior (auto-resolve account_id), format (e.g., destination_number), and interdependence (greeting_text requires destination_number). This adds immense value beyond the bare schema.

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 it updates mutable settings of a tracker (name, destination, whisper, greeting, SMS). It distinguishes from siblings like delete_tracker (which disables) and other update tools by specifying tracker-specific fields.

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?

Explicitly says when to use (update mutable settings) and when not to use (disable via delete_tracker, permanent removal via support). Also warns that setting 'status' is silently ignored. Provides clear alternative actions.

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