notion_get_user

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

With no annotations provided, the description carries the burden of disclosing behavior. It states the tool 'Get details' (implying non-mutating) and lists the return fields. It also specifies the user_id format as a 'Notion user UUID.' However, it does not mention error conditions (e.g., 404 if not found) or any authentication requirements, but for a simple read tool this is reasonably transparent.

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 three concise sentences: purpose, return values, and usage guidance. It is front-loaded with the primary action. No filler or redundant information; every sentence earns 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 simple get-by-id tool with one parameter and an output schema, the description is complete. It states what the tool returns, how to find the ID (via list_users), and the parameter format. No additional behavior or caveats are needed for this straightforward read operation.

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%, but the description compensates by defining user_id as 'Notion user UUID,' which adds meaning beyond the bare schema (type string, title 'User Id'). It also includes the context that the ID is for a specific user. This is sufficient for a single parameter tool.

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 a specific verb+resource+scope: 'Get details for a specific Notion user by ID.' It also lists the returned fields (name, email, avatar URL, type), distinguishing it from sibling tools like notion_list_users which list users rather than fetching one. The phrase 'by ID' further clarifies the exact operation.

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 explicitly guides usage: 'Use notion_list_users to find user IDs first.' This provides a clear alternative and prerequisite, telling the agent when to use this tool vs. listing users. It also implies this tool is for a known user ID, which is good contextual guidance.

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