get_recent_activity

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful fact that events come from the FreeCAD observer and enumerates event categories, but says nothing about ordering (newest first?), truncation, or whether an empty result means no activity vs. no observer running.

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 tight sentence that front-loads the verb and resource with no filler. It is efficient, though the brevity comes at the cost of the missing scope and parameter detail noted elsewhere.

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?

An output schema exists, so return-value explanation is not required, and annotations carry the safety profile. However, for a filtered activity-feed tool the undefined "recent" window and the unexplained doc_name scoping are gaps an agent needs filled before calling confidently.

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% and yet the description never mentions either parameter. It does not explain what limit bounds (count of events? default 25?) or how doc_name scopes results versus returning global activity, so it fails to compensate for the undocumented schema.

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?

Specific verb ("Read") plus a clearly scoped resource (recent events recorded by the FreeCAD observer) with concrete examples (edits, undos, dialogs). It is distinguishable from siblings like get_console_output or get_undo_redo_status, though no sibling is named to reinforce that distinction.

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 states what the tool returns but gives no guidance on when to prefer it over get_console_output, get_undo_redo_status, or get_document_graph. "Recent" is never defined as a time window or ordering, so an agent cannot judge whether this data satisfies its need.

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