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

Annotations already declare readOnlyHint and destructiveHint=false, yet the description adds non-obvious operational context: calls count toward account usage and are recorded in the user's activity log, and the newsletters source appears conditionally. These are quota/audit traits an agent cannot infer from 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?

Four sentences, front-loaded with the resource and its contents before the usage and constraint notes; no filler. Minor redundancy in restating 'Read-only', which the annotations already assert, though it is bundled with the new usage-logging detail.

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?

No parameters and no output schema, so the description must (and does) enumerate the returned fields itself, and it covers cost, audit logging, and the conditional newsletters source. Nothing an agent needs in order to call and interpret this tool is missing.

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 is empty at 100% coverage, so there is nothing for the description to disambiguate. Baseline for a 0-param 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 and resource and enumerates exactly what is returned: source status, saved-post counts, last sync times, reconnection status, plus the newsletters source when forwarding is in use. Siblings are all save/collection tools, so confusion is unlikely, though the description never explicitly routes against them.

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?

'Use to check which imported sources are available' gives a clear use case, and 'Does not connect, reconnect or sync any platform' explicitly rules out the adjacent actions an agent might otherwise attempt. No alternate tool is named for those excluded actions, so it falls short of a full when/when-not/alternative statement.

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