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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds only the action enumeration, which already exists in the enum, plus the help pointer. No return shape, no auth or rate-limit context — little value beyond 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?

Two sentences, front-loaded with what the tool returns before the action list. The enumeration partly duplicates the schema enum, but the text is tight and free of 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?

There is no output schema, so the description must carry return-value meaning; it names the resource families but never says what each action yields. With ten actions and a free-form nested params object, it leans entirely on a runtime 'help' call rather than being self-sufficient for selection.

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 50%: params is described but action is an undocumented enum of opaque values like 'analytics_home' and 'analytics_selection'. The description reproduces the enum list without explaining what any action means or returns, though the 'help' action is a meaningful discovery mechanism the schema does not describe.

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?

The description states the resource set clearly — dashboard, stats, time-away summary, analytics and LinkedIn suggestions — so an agent knows this is a read-only insights multiplexer. It does not, however, differentiate itself from sibling read tools like get_membership or get_profile, leaving overlap to inference.

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?

The only guidance is operational: 'Call with action "help" for each action's fields.' There is no statement of when to pick this tool over get_membership, get_profile, or other get_* siblings, and no indication of which action suits which question.

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