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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing behavioral — only a pointer that describe_operation provides native request schemas, with no note on what data is returned or how 'recent' is bounded.

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?

Extremely short but wasteful — the identical sentence is duplicated, and an opaque operation ID is given without purpose. It is not front-loaded with any actionable information.

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?

For a tool with nested/arbitrary query params, no output schema, and 0% schema description coverage, the description leaves the agent unable to know what 'recent activity' contains, its time window, or how to shape the query. It is functionally inadequate.

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 the two parameters (a free-form `query` object and an empty `params` object) are undocumented. The description provides no parameter meaning; its only aid is redirecting to describe_operation for native schemas, which is marginal.

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 is just the URL path 'GET /api/dashboard/recent-activity' repeated verbatim, which merely restates the tool name (get_dashboard_recent_activity) in path form. It conveys a resource ('recent activity') but no scope, content, or differentiation from dashboard siblings like get_dashboard_metrics or get_dashboard_upcoming_events.

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 when to prefer this over the many other dashboard tools. An agent learns nothing about selection criteria from the text.

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