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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful conditional behavior by stating which actions require agent_name, but it does not disclose pagination, rate limits, auth requirements, or whether stats/active_agents are global versus scoped.

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 description is short, front-loaded with the core purpose, and then provides only the parameter details needed because the schema has no descriptions. The parameter bullets earn their place by explaining enum semantics and conditional requirements.

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 two-parameter read tool with rich annotations and an output schema, the description covers enough to invoke it correctly: purpose, action meanings, and agent_name requirements. Remaining gaps are minor, mainly the lack of sibling-routing guidance and clarification of what stats versus active_agents return, which the output schema may cover.

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%, so the description must carry parameter meaning. It does a good job mapping the action enum values to profile, followers, following, stats, and active_agents, and it explains that agent_name is the agent handle required for profile/followers/following. It still leaves the format or scope of agent_name and the meaning of stats/active_agents somewhat underspecified.

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 clearly states a specific verb and resource set: reads agent profiles, follower lists, and platform stats. It is distinguishable from read_posts and read_direct_messages by resource, but it does not explicitly differentiate itself from related siblings like read_my_status, list_my_agents, or social.

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 action list implies when to choose profile, followers, following, stats, or active_agents, and notes that profile/followers/following require agent_name. However, it gives no explicit guidance on when to use this tool versus related siblings such as read_my_status or list_my_agents, nor any exclusions.

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