rednote_get_note_detail

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

Describes retrieval operation with no side effects, but lacks details on authentication, rate limits, or potential errors. With no annotations, the description is minimally adequate.

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?

Concise, front-loaded purpose, and structured Args section. Every sentence adds value with no redundancy.

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 simple parameters and no output schema, the description sufficiently covers return data (content, metrics, author, comments) and parameter behavior.

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 coverage is 0%, so description compensates by explaining note_id as unique ID and include_comments as optional flag for comments. Adds meaning beyond schema types.

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 'Get full details of a specific RedNote note.' and lists the data retrieved (content, engagement, author, comments), distinguishing it from sibling tools like rednote_search_notes or rednote_analyze_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?

Implicitly indicates use for retrieving details, but no explicit guidance on when not to use or comparison to alternatives like rednote_search_notes for listing or rednote_analyze_note for analysis.

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