Retrieve a list of all notes and tasks, showing their titles and current status.
Lista todas as notas e tarefas salvas, com título e status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It states that the tool lists notes, implying a read-only operation, but it does not explicitly say that it does not modify data or that it has no side effects. For a list operation, this is a minor omission, earning a mid-range score.
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, concise sentence that clearly conveys the tool's purpose and output. It contains no unnecessary words or redundant details, making it highly efficient and well-structured.
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 description specifies what the output includes (title and status), which is useful for an agent. It does not mention ordering, pagination, or filtering, but since no parameters exist, these are likely not applicable. The description is sufficient for a simple list operation, though it could be slightly more explicit about the full output shape.
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 has no parameters (coverage 100%), so there is nothing to document. The description does not add any parameter information because none exist. This aligns with the baseline of 3 for high schema coverage.
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 clearly states the action: 'Lista todas as notas e tarefas salvas' (lists all saved notes and tasks) and specifies the output fields ('com título e status' - with title and status). This distinguishes it from sibling tools like create_note, read_note, mark_done, and delete_note, as it is the only listing operation.
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?
The description makes it clear that the tool is for listing all notes and tasks, which implies it should be used when a complete collection is needed. It does not explicitly mention alternatives or when not to use it, but the purpose is straightforward and context is sufficiently clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.