Notion MCP Server

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

With no annotations, the description carries full burden but only states 'retrieve' without behavioral details. It doesn't disclose if it's read-only (implied but not explicit), rate limits, authentication needs, error handling, or response format. This is inadequate for a tool with zero annotation coverage.

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 extremely concise ('Notion | Retrieve a user') with no wasted words. It's front-loaded with platform and action, making it easy to scan. Every element (platform, verb, resource) earns its place efficiently.

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 no annotations, 0% schema coverage, no output schema, and 1 parameter, the description is incomplete. It lacks details on behavior, parameters, output, and usage context. For a retrieval tool, it should at least hint at return values or authentication, but it doesn't.

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%, so the description must compensate but adds no parameter information. It doesn't explain 'user_id' (e.g., UUID format, where to find it, or examples). With 1 required parameter undocumented, the description fails to provide meaningful semantics beyond the schema.

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 'Notion | Retrieve a user' clearly states the action (retrieve) and resource (user) with platform context (Notion). It distinguishes from siblings like 'API-get-users' (plural) and 'API-get-self' (specific user), though not explicitly. However, it lacks specificity about what 'retrieve' entails (e.g., returns user details).

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 provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), differentiate from 'API-get-users' for listing users or 'API-get-self' for current user, or specify use cases (e.g., fetching a user by ID for permissions).

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