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

Annotations already signal readOnlyHint=true and idempotentHint=true, so the safe, non-mutating nature is covered. The description adds value by disclosing the team scope and the specific categories of information returned, which is exactly the behavioral context an agent needs beyond the annotations.

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 with no filler: the first states what the tool does and its scope, and the second lists the return content. Every sentence earns its place and the key action is front-loaded.

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?

Given zero parameters, read-only and idempotent annotations, and the existence of an output schema, the description is complete. It covers scope, expected output, and the non-mutating nature, leaving no ambiguity about how or why the tool should be called.

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 has zero parameters, so there are no parameter semantics to document. The description correctly avoids inventing parameters and focuses on behavior; the schema coverage baseline of 4 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?

The description opens with the specific verb 'Get' and identifies a clear resource: a summary of autonomous agent activity for the authenticated user's team. It further clarifies purpose by enumerating the summary's contents (enabled agents, recent actions, per-agent stats, pending approval counts), which distinguishes it from sibling tools like get-person-activity-tool.

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 description provides clear context by scoping to the authenticated user's team and stating the tool returns a summary plus exact output categories. It does not explicitly state when not to use it or name a sibling alternative, but for a zero-parameter read-only summary tool, the context is sufficient.

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