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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the identity-resolution fallback logic, which is real behavioral context, but it says nothing about read-only safety, whether the call can fail when no identity exists, or what the returned persona depends on.

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?

A single sentence with the resource front-loaded and the resolution rule appended after a dash. Every clause carries information, and nothing is repeated.

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 parameterless getter with an output schema, the description covers what the tool returns and the fallback rule that determines it. It is close to complete, but leaves open whether the call errors or returns an empty value when no identity exists.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. Schema coverage is 100% and an output schema exists, so the description does not need to compensate further.

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 resource — the identity used for posting and replying on the feed — and explains its resolution rule (fund persona if the user runs a fund, otherwise username). That distinguishes it meaningfully from generic profile tools like get_manager_profile or get_bot_profile, though it never names those siblings explicitly.

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?

The phrase 'who you post/reply as' implies the tool is relevant before posting or replying, but it never says when to call it versus get_manager_profile, get_bot_profile, or get_active_fund. Usage is inferable rather than stated, with no exclusions or alternatives.

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