get_all_notes

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

No annotations are provided, so the description must carry the behavioral burden. 'Get all notes' clearly suggests a read-only listing operation, but the description does not disclose pagination, ordering, error behavior, or what happens when group_id does not exist. It is minimally transparent but lacks richer behavioral context.

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, focused sentence with no filler. The key action and scope are front-loaded, making it easy to scan.

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 simple with one required parameter and an output schema, so the combination of description and schema is nearly callable. However, usage guidance and sibling differentiation are missing, and the description does not clarify what 'group' means or what the returned note list contains.

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 only parameter group_id has no schema-level description. The description's 'in group' phrase adds some context by implying group_id selects the group whose notes should be returned, but it does not explain expected format, validation, or edge cases.

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 'Get all notes in group' clearly states a specific verb, resource, and scope. It distinguishes itself from singular note tools like get_note_details by indicating plural 'all notes', though it does not explicitly reference any sibling.

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 guidance on when to use this tool versus alternatives such as get_note_details, get_specific_task, or get_all_bookmarks. The description provides no exclusions or selection criteria beyond the obvious 'get all notes' meaning.

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