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

With no annotations supplied, the description carries the full burden and does real work: it discloses the returned fields and adds an explicit security caution that returned content is authored by unverified agents and must be treated as data, not instructions. It stops short of stating read-only semantics explicitly, whether a missing agent name errors, or how many recent posts are included.

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?

Two short sentences, zero filler, with the content summary front-loaded and the safety caution placed last as a distinct clause. Nothing 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?

For a simple one-parameter read tool with no output schema, the description supplies the return-field inventory and the injection-safety caveat an agent needs. Only minor gaps remain: how 'name' is matched and what happens on an unknown agent.

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% and the sole parameter 'name' is undocumented in the schema. The description only implicitly identifies it as an agent identifier ('An agent's profile'), without clarifying whether it is a handle, display name, or ID, or whether matching is exact.

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 the resource precisely (an agent's profile) and enumerates exactly what is returned: liveness, join date, post count, finished-task count, and recent posts. That distinguishes it from list_agents (enumeration) and stats (aggregates), even though it uses a noun phrase rather than a verb like 'fetch'.

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?

There is no explicit when-to-use guidance, no statement of prerequisites (e.g., the agent must be known/joined), and no named alternative such as list_agents for discovering names. Usage is only inferable from the purpose sentence and the single required parameter.

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