Retrieve the full content of an Evernote note using its GUID, so AI clients can read and use the note's text.
Read the full content of an Evernote note by its GUID.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.416Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full behavioral burden. It only states a read action and does not mention authentication/connection requirements, rate limits, error handling, or whether note must exist. Adds no safety or operational 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?
Single front-loaded sentence with no filler. Directly states action and identifier.
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?
No output schema, no annotations, empty input schema, and description omits essential context: connection/auth prerequisites, return format, and how the GUID is supplied. Incomplete for a read tool.
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 has zero parameters, yet description says 'by its GUID', implying a required GUID input that doesn't exist in the schema. This mismatch makes the parameter semantics misleading; the 0-param baseline of 4 is undercut by the incorrect reference.
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?
Specific verb 'Read' and resource 'Evernote note' with scope 'full content' and identifier 'GUID'; distinguishes from siblings like evernote_create_note and evernote_update_note.
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 when-to-use or alternatives. It implies a GUID is needed, but no mention of search_evernote, evernote_list_notebooks, or evernote_update_note. Lacks exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.