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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered elsewhere. The description adds only the word "home," hinting at personal vs. team scoping, but discloses nothing about filtering behavior, pagination via cursor, or default result windows despite the range param defaulting to 7d.

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?

A single clean, front-loaded sentence with zero wasted words. But for a tool with nine filter parameters, this level of terseness is under-specification rather than effective conciseness.

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 nine parameters, no output schema, and 0% schema coverage, the description should carry much more weight. It leaves filtering semantics, the today/7d/30d/custom range behavior, and pagination entirely undocumented, which is inadequate for this tool's complexity.

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 0% across 9 parameters, yet the description mentions none of them. Filters like q, types, range, syncIds, calendarIds, and the cursor pagination token are completely unexplained anywhere, so the description fails to compensate for the coverage gap.

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?

"Read your home activity feed" states a verb (read) and a resource (home activity feed), so it is not a tautology. However, "activity" is never defined (sync runs? file changes? calendar changes?), and it does not distinguish itself from siblings like list_events or list_sync_runs. An agent gets the general idea but not the scope.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. The description never says when this feed should be consulted instead of list_events, list_syncs, or list_sync_runs. The agent must infer usage entirely.

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