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

The description narrates a data-recording mutation ('record what happened', 'nothing is recorded', 'clear lifts an earlier do_not_contact' — all state-changing), yet annotations declare readOnlyHint=true and destructiveHint=false. This directly contradicts the declared safety profile, so the agent gets a false signal about whether the tool writes anything.

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?

Dense but front-loaded with the core action and account context, then outcome semantics, then scope guidance. Every sentence carries information, though the single-block paragraph could be split for scanability.

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?

Covers scope modes, outcome semantics, input validation failure behavior, and history privacy, which is thorough for a 4-param mutation with no output schema. The one substantive gap is the annotation conflict, which undermines the otherwise complete behavioral picture.

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 coverage is 100% and enums are self-documenting, but the description adds real meaning the schema lacks: 'clear' undoes a prior do_not_contact, scope 'person' requires contact_id, and passing an email address is an implicit prohibited parameter that causes refusal.

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?

Specific verb (record) plus resource (podcast outreach outcome) with explicit scope. It also names the sibling it affects, find_podcast_contacts, so an agent can distinguish it from the discovery-side tools in the sibling list.

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?

It states the trigger ('when you reached out to a podcast') and gives explicit conditions for the person-level mode, including where to get contact_id (get_podcast_profile). It stops short of full when/when-not framing against other siblings, but the routing is clear.

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