note_info

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

No annotations provided, so description carries full burden. It states metadata retrieval and default behavior but does not disclose any limitations, side effects, or authorization needs. Minimal but accurate.

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 sentence that efficiently communicates the core purpose and default behavior. No wasted words, but could benefit from listing metadata types explicitly.

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?

Given an output schema exists, return value explanation is not needed. However, the description lacks context on when to use this tool over siblings and does not explain parameter usage. Adequate for a simple tool but incomplete for the complex sibling set.

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 description only mentions defaulting to active note. Does not explain the difference between 'file' and 'path' parameters or how they relate to the active note concept. Adds the default context but lacks parameter-specific guidance.

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?

Clearly states the tool shows metadata for a note, listing specific types (size, dates, counts) and defaults to active note. Distinguishes from siblings by focusing on metadata rather than content or properties.

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 explicit when-to-use or when-not-to-use guidance. With 20 sibling tools, the description should indicate when to prefer this over related tools like read_note or list_properties. The default behavior is mentioned but no alternatives.

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