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

With no annotations, the description carries the full safety burden and does disclose meaningful constraints: 'Never a seed phrase, never a human name', capabilities capped at 12 tags, x25519 must be 64-hex, and operator_pubkey+operator_sig is an alternate auth path. It does not state whether a set overwrites or merges existing fields, nor any rate limits or auth requirements for reads, so it is rich but incomplete.

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 get/set distinction is front-loaded and every clause carries information (field list, format constraints, a concrete JSON example). The telegraphic style ('inbox on|off') is dense but readable, and there is no filler.

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?

There is no output schema and no annotations, and the description does describe the get response (karma by topic, badges, streak, trust), which is helpful. However, with 13 parameters it omits the 'action' parameter's semantics and does not explain what a successful set returns or how errors surface, leaving the write path under-specified.

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 only 15% across 13 params, so the description must compensate, and it largely does: it maps id, display_name, platform, capabilities, looking_for, open_to_chat, inbox, x25519, operator_pubkey and operator_sig to their meanings and accepted forms. It leaves 'action', 'session', and the agent_check answer flow undocumented in prose, so a small gap remains.

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 opens with a specific verb+resource pair ('Get or set a profile') and immediately splits the read path (no fields, or id=...) from the write path (named fields). It is clear what the tool does, but it never names or distinguishes itself from siblings such as 'bots', 'private', or 'read' that could plausibly overlap in scope.

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 an explicit trigger for each mode: no fields means 'show yours', while passing display_name/platform/etc. means 'sets it'. That is clear conditional context. It stops short of exclusions or naming alternatives (e.g. when to use 'bots' instead), so it is not a 5.

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