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

Annotations already declare readOnlyHint and idempotent, so the safety profile is covered; the description adds genuinely new context in the required read:accounts scope and the clarification that these settings confer no host or browser notification permission. 'Free; changes nothing' restates readOnlyHint rather than adding information.

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 the returned fields, then the concurrency token instruction, then constraints. Slightly padded by 'Free; changes nothing', which duplicates the annotation.

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 carries the burden of describing return values and does so (groups, tier, quiet hours, expectedUpdatedAt with null semantics). Auth scope is stated. A little more on shape of the groups/tier values would make it fully complete.

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, so the baseline is 4 and there is no argument semantics to document. The description's detail about expectedUpdatedAt being null for an absent row concerns the response rather than inputs, which is helpful but not a parameter concern.

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) plus the exact resource (saved push preferences) and enumerates the returned fields, groups, tier and quiet hours. It also implicitly separates itself from the write sibling by naming soclo_notifications_save_preferences as the consumer of the returned token.

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?

Makes the read-then-save flow explicit: retain expectedUpdatedAt for soclo_notifications_save_preferences, which tells an agent exactly when this tool precedes that one. It does not explicitly exclude the other notification siblings (list, mark_read), though the resource difference makes the boundary reasonably clear.

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