iam_desktop_profile

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

With no annotations, the description carries the burden well: it discloses that avatar_path intentionally publishes a local file with a 1 MB cap and accepted formats, that empty values clear fields, and that all content is publicly visible. It does not state whether partial updates are merged vs. replaced or whether write permission/ownership is required.

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 and front-loaded: the action and field inventory come first, constraints follow. The long parenthetical field lists make it slightly hard to scan, but no sentence is redundant.

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?

An output schema exists, so return values need no explanation, and the behavioral/field coverage is strong. The gap is the parameter layer: 0% schema description coverage plus an entirely unexplained `mailbox` argument and unstated nesting under `updates` leaves an agent without enough to construct a correct call from the description alone.

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 0%, so the description must compensate, and it does richly for the profile fields (presence enum values, 2000-char limit, #RRGGBB format, clearing semantics, avatar size/type limits). However, it never mentions the `mailbox` parameter nor explains that these field names are keys nested inside the `updates` object, which is a real risk of malformed calls.

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 states a specific verb pair (inspect/update) applied to a specific resource (buddy profile) and enumerates every writable field, so the scope is unmistakable. It stops short of naming a sibling (e.g., iam_whoami for read-only identity, iam_friend for relationships), so an agent must infer the boundary rather than being told.

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?

"Only intentionally public profile content belongs here" and "Presence and away messages are chosen expression, not runtime availability, wake blocking, or authority" are explicit scope exclusions that prevent real misuse (e.g., using presence to signal wake availability). No positive routing to alternatives is given, so it sits just below a 5.

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