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

Beyond annotations that already mark this as read-only/idempotent, the description discloses sort order, per-status counts, and the cancelReason field semantics with a concrete example. This tells the agent what kind of data to expect without needing an output schema.

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?

Three sentences, each with a distinct purpose: action/result, use case, and a helpful detail about cancelled entries. It is appropriately sized and front-loads the core behavior.

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 provides the essential return semantics (sorted entries, counts, cancelReason). It does not enumerate all entry fields or explain pagination, but for a simple node-activity read with annotations covering safety, the remaining gaps are minor.

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%, so the description must carry parameter meaning. It clarifies that nodeId targets a specific workflow node, but it never mentions the limit parameter, its default, or how it controls returned entries. The schema's self-descriptive 'limit' and default value keep this from being a lower score.

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 clearly identifies the action ('Get recent activity') and resource ('specific workflow node'), and adds return-shape details like sorted entries and per-status counts. It does not explicitly differentiate this tool from sibling workflow tools such as get_workflow_stats or list_leads_at_node, so it falls one step short of a full 5.

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?

'Useful for monitoring execution progress and identifying failures' gives concrete when-to-use context. It does not provide exclusions or name alternative tools, so it is not a complete routing guide.

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