Retrieve User

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds a behavioral constraint: requiring an enterprise plan and specific API key to avoid permission errors. This adds useful context beyond the annotations, though it does not detail other aspects like rate limits or response structure.

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 two short sentences with no extraneous content. The core purpose is stated first, and the prerequisite note is added as a second sentence. Every sentence adds value.

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 simple retrieval tool with annotations and complete schema, the description is fairly comprehensive. It covers purpose and a key prerequisite. However, it lacks any detail about the return object, which might be expected since there is no output schema. Still, it is adequate for the complexity level.

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 100%, with detailed descriptions for both parameters (user_id format and format enum usage). The description does not add further parameter semantics beyond what the schema provides. Baseline of 3 is appropriate.

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 'Retrieve a specific user by user_id in Notion', specifying the verb (retrieve), resource (user), and unique identifier (user_id). This distinguishes it from sibling tools like notion_list_all_users (list all) and notion_retrieve_bot_user (bot user).

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 includes a prerequisite note about the Notion Enterprise plan and Organization API key, which is helpful. However, it does not explicitly state when to use this tool versus alternatives (e.g., list all users first if ID unknown, or use notion_retrieve_bot_user for bot users). No when-not or exclusion guidance is provided.

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