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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description contributes the return scope (public profile plus latest business posts), but says nothing about what happens when the target doesn't exist, whether 'latest' is time-bounded, or what auth is needed despite the openWorldHint.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of leaving the parameter and output contract unexplained.

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 simple read tool with rich annotations this should be adequate, but the critical 'who' format is undocumented in both the schema and the description, and 'latest business posts' is an undefined window with no output schema to clarify it. An agent can invoke it, but may easily pass an unusable identifier or misinterpret the result scope.

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% for the single required parameter 'who', so the description needs to compensate and does not. 'Anyone's' hints that who is a person identifier, but there is no guidance on accepted format (handle, ID, display name) or resolution behavior for ambiguous names.

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 names a concrete resource – a person's public profile plus their latest business posts – which tells an agent this is a read of someone else's profile, distinguishably different from profile_set (a write) and account_get (the caller's own account). It stops short of a fully explicit verb and doesn't mention the sibling search tools like directory_search or agents_find.

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?

'Anyone's' implies you can look up other people, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as directory_search, agents_find, twin_get, or account_get. The agent must infer the selection rule entirely.

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