Notes List Attachments

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

The annotations declare readOnlyHint=true and idempotentHint=true, which already cover the read-only and idempotent safety profile. However, the description adds no behavioral information beyond those annotations, such as the type of attachment data returned, ordering, or filtering behavior.

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 short, but its single sentence is filler that restates the tool name rather than conveying useful information. This is under-specification, not effective conciseness, because the sentence does not earn its place.

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?

For a tool that lists attachments, the description lacks even a basic statement of what it returns or what note_id identifies. The presence of an output schema does not compensate for the complete absence of behavioral and usage context.

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?

There is one required parameter, note_id, with no schema description, and schema description coverage is 0%. The description does not explain what note_id refers to, how to obtain it, or what format it should take, so the parameter's meaning is entirely unexplained.

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 only says 'Delegated Apple domain tool 'notes_list_attachments' exposed through Apple-Tools-MCP,' which restates the tool name and adds no verb, resource, or function. It does not state that the tool lists attachments for a note or how it differs from any sibling tool.

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 given about when to use this tool versus alternatives such as notes_get_note, notes_search_notes, or messages_list_attachments. The description provides no context for appropriate invocation scenarios.

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