ads_client_profile_create

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

With no annotations, the description carries the full burden; it does disclose that consent defaults to unknown and that no message is sent. It omits behavior an agent would want for a write tool: idempotency, what happens on duplicate telegram_user_id, and what identifier is returned.

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?

Four compact sentences with the core action front-loaded and no filler. The channel/connector detail is dense but each clause maps to a real parameter.

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 15-parameter creation tool with no annotations and no output schema, the description leaves major gaps: the required telegram_user_id is unmentioned and the return value (presumably a new profile id) is not described. It reads like parameter footnotes rather than an operating guide.

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 0% across 15 parameters, so the description must compensate. It explains only channel, external_user_id, contact_account_id, and the consent default, leaving id, source, status, context, metadata, username, display_name, next_action_at, last_contact_at, dialogue_summary, and the required telegram_user_id undocumented.

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?

States a specific verb and resource ("Create a local client profile with per-person context") and clarifies that the profile is a local record. This clearly separates it from the messaging siblings, though it never explicitly contrasts with ads_client_profile_update or ads_client_profile_get.

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 gives channel-selection guidance ("Telegram remains the default channel; channel and external_user_id can represent Mastodon or another connector") and one useful exclusion ("this tool does not send a message"). However, it never states when to create versus when to update/upsert, nor prerequisites such as a connected account.

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