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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it reads only what Narrareach has persisted and does not live-refresh platform connections, and it scopes itself to the personal account.

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 dense paragraph, but front-loaded with the verb+resource and the field inventory that an agent needs. The enumeration of every platform (Substack, LinkedIn, Instagram, Threads, Facebook, TikTok, Pinterest, X) is longer than strictly necessary, though it is informative rather than filler.

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?

An output schema exists, so return shape need not be described. The description covers scope, the mutation alternative, the stored-vs-live distinction, and the personal-account limitation, leaving no meaningful gap for a parameterless read 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?

The tool takes zero parameters and the schema confirms an empty object, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies.

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 ("the writer's main Narrareach Settings") and then enumerates exactly what is included: preferences, per-platform default accounts, connection health, and email notification settings. It clearly distinguishes itself from update_settings, the sibling that mutates the same resource.

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?

Explicitly routes mutation to the alternative ("Change preferences with update_settings") and states a boundary condition ("Reads what Narrareach has stored; it does not refresh connections with any platform"), which implicitly points at the refresh_* siblings. It does not, however, spell out when a caller should prefer this over adjacent read tools like get_user_profile.

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