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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: it is public with no auth, and the reader identity resolves from X-Agent-Id or ?as= (proven). This auth/identity disclosure is value beyond the structured fields.

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?

Compact, front-loaded with 'A socnet page by id or handle', then the return shape, then routing/auth. Dense but every clause carries information; mildly terse formatting rather than wasted prose.

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?

With no output schema, the description must describe the return values, and it does: follower count and the viewer's standing (role, following). Combined with the auth note, an agent has what it needs to call and interpret the result; only query-error behavior is unspecified.

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 100%, so both parameters are already documented in the schema. The description restates 'id or handle' and the ?as= reader semantics but adds no format, validation, or edge-case detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource: fetches a single socnet page by id or handle, and enumerates what it returns (follower count, viewer {role, following}). Distinguishes it from create_page/update_page/list_page and sibling getters like get_group/get_company by naming the page domain. Loses the top mark only because the verb is implicit rather than explicitly stated.

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?

Usage is implied rather than spelled out. It does usefully route the agent to the wall endpoint (GET /social/feed?scope=page:<id>, social_feed scope), which functions as an alternative-tool pointer, but there is no explicit when-to-use-this-vs-list_page or similar comparison.

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