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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld=false), the description discloses that reconciliation may refresh canonical projections, that cursor values come from prior responses, that unknown history is not zero, and that communication returns receipt timing and the immutable approved design rather than a reconstructed personalized body. These are meaningful behavioral caveats that annotations do not carry.

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?

Front-loaded with the verb and resource, and every clause carries actionable information. The action list and ID-format details make some sentences run long, but there is little filler to cut.

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 and nine distinct actions, the description only characterizes the return shape for communication; purchases, history, membershipHistory, permissions, activity and events returns are left unspecified. It covers identity/scoping well but is not fully complete for a multi-action inspection tool.

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 coverage is only 50% and payload is a free-form object, so the description must compensate — and it does, specifying ID formats (u_/e_), the listId/contactId alternatives, communityId scoping, the campaignId+deliveryId requirement for communication, and expectedRevision/draft/cursor expectations. It adds substantial meaning over the generic schema payload description.

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 (Read) and resource (canonical scoped Network profile) and enumerates the nine supported actions, so an agent knows exactly what domain this covers. It does not, however, explicitly contrast itself with plausible siblings such as list_my_network or get_account_status.

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?

Gives concrete selection criteria: supply personId (u_ account ID or e_ destination hash) or listId/contactId, with optional communityId selecting an authorized community, and notes that communication additionally requires campaignId/deliveryId from communications. It also points to a workflow guide resource. It stops short of explicit when-not-to-use or naming an alternative sibling.

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