devbook_get_stats

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

No annotations are supplied, so the description carries the full burden. It does add genuine value by naming the five aggregate figures returned, which is the only signal about the result shape since there is no output schema. However, it says nothing about scope (global vs per-project/per-user), permissions required, or whether the read triggers any side effect, leaving those behavioral questions unanswered.

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 sentence with the action and resource front-loaded and the returned metrics in a compact parenthetical. No filler or repetition; the only mild weakness is that the parenthetical stacks five items without grouping, but every element carries 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 zero-parameter read-only stats call with no output schema and no annotations, the description supplies the essential missing piece – what the counts are. The remaining gap is scope: it does not say whether statistics are system-wide or scoped to a project/user, which an agent would want before trusting the numbers.

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 takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The parenthetical list describes output content rather than inputs, which is appropriate for a no-argument call.

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 uses a specific verb ('Get') plus a clearly scoped resource ('system statistics from Devbook') and enumerates exactly which metrics come back: total prompts, projects, attachments, pinned prompts, standalone prompts. That enumeration makes it obviously distinct from the single-entity siblings like devbook_get_project and devbook_get_prompt, though it never explicitly contrasts itself with them.

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?

Usage is only implied by the word 'statistics' – an agent can infer this is a read-only aggregate call for overview/counting purposes, but the description gives no explicit 'use this when you need counts rather than records' guidance or any exclusion against the get_* / list_* siblings.

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