apple_notes_stats

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

No annotations provided; description does not disclose behavioral traits such as read-only nature, permissions required, or performance characteristics. For a stats tool, it omits crucial transparency beyond the basic function.

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?

Single sentence that efficiently conveys the tool's output without unnecessary words. Perfectly structured for quick comprehension.

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?

Given zero parameters, no output schema, and the simple nature of a stats tool, the description sufficiently covers what the tool returns. Could be expanded with a note about data scope, but adequate for its simplicity.

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 with 100% schema coverage. Description adds no parameter info because none exist, but the baseline for 0 params is 4. No additional meaning is needed beyond the purpose statement.

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?

Description states specific verb ('Get') and resource ('aggregate statistics') and lists exactly what is returned: total notes, notes per folder, date range. This clearly distinguishes it from sibling tools like 'apple_notes_list' (lists notes) and 'apple_notes_by_folder' (notes by folder).

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?

Implied usage: use when aggregate statistics are needed. No explicit when-to-use or when-not-to-use guidance, nor comparison to alternatives. Lacks direction for AI agent to differentiate among sibling tools.

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