update_profile

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

No annotations provided, so description carries full burden. Discloses that changes propagate immediately and that remove_avatar must be set to true to clear photo. Does not mention permissions, rate limits, or failure modes, but for a profile update this is adequate.

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 well-structured sentences, front-loaded with purpose, then parameter details, then usage guidance. No wasted words; every sentence earns its place.

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?

Tool has no output schema and no complex dependencies. Description covers main behavioral traits (immediate propagation), parameter semantics, and usage boundaries. Does not specify return value, but for an update tool that is 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?

Adds significant value over schema: explains name is shown to contacts who haven't saved your number, about is bio, avatar_path must be local JPEG/PNG, and remove_avatar clear without new image. Also clarifies all optional. Schema has 100% coverage but description enriches 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?

Clearly states the tool updates the user's own Signal profile, listing specific fields (name, about, avatar_path, remove_avatar). Differentiates from siblings like get_profile, update_device, and update_configuration by explicitly saying what NOT to use it for.

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?

Provides explicit when-to-use context (updating own profile) and when-not-to-use (renaming device, changing messaging settings), naming alternative tools for those cases. Also notes all parameters are optional.

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