system_get_recap

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

No annotations and the description carries no behavioral information: no mention of permissions, caching, rate limits, or what 'recap' covers. It adds nothing beyond the route.

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 that shortness is under-specification, not conciseness. The tag line is boilerplate that adds no value.

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 stats endpoint sitting among ~20 system_* siblings, the description provides nothing an agent needs to decide whether to call it or what it returns (no output schema either).

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?

Zero parameters, so the baseline is 4. Nothing to document, and the empty schema is consistent with the description.

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 essentially the HTTP route plus the OpenAPI summary 'Get Recap' and a controller tag. It restates the tool name rather than explaining what a 'recap' actually contains or how it differs from other system stats siblings like system_get_stats, system_get_stats_digest, or system_get_metadata.

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?

No guidance on when to use this tool, when not to, or which sibling stats endpoint to prefer. Given the dense cluster of system_get_* stats tools, this is a serious omission.

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