list_manual_entries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond that—no mention of pagination, default limits, ordering, or what qualifies as a manual entry. It essentially restates the tool name.

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?

The description is a single, short sentence, which is structurally concise. However, it borders on a tautology and lacks useful detail, so it does not earn a higher score for conciseness; under-specification prevents it from being truly helpful.

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?

The tool is contextually sparse: no explanation of what manual entries are, no output schema to compensate, and no guidance on when to choose this over sibling tools like list_manual_entry_files or list_journal_entries. The openWorldHint suggests unfiltered results, but pagination and domain specifics are absent.

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 schema provides 100% coverage for both parameters (limit and offset) with clear descriptions. The tool description adds no parameter information, but the baseline of 3 applies because the schema fully documents parameter semantics.

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 the verb 'Fetch' and specifies the resource 'manual entries', giving a clear high-level purpose. It does not explicitly differentiate from siblings like list_manual_entry_files or list_journal_entries, but the naming is distinct enough to infer the target resource.

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 is provided on when to use this tool versus alternatives. The description lacks any mention of context, prerequisites, or exclusions, and does not reference related search or list tools.

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