notion_export_get_result

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get,' which implies a read operation, but it does not state whether the tool is read-only, what the result contains, whether it blocks or returns immediately, or any error conditions. This is minimal and mostly inferred from the verb.

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 short (4 words) and front-loaded, but it is under-specified rather than appropriately concise. It omits critical context that should accompany a tool of this complexity, making it less useful than a longer, more informative description.

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 there is no output schema, no annotations, and only 2 parameters, the description is inadequate. It does not explain what the export result looks like, how the 'recursive' parameter affects the result, or the relationship between id and the export process. The tool feels incomplete without these details.

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?

The input schema provides 100% coverage with descriptions for both parameters (id and recursive). The description adds no additional parameter context, but the schema already documents their purpose. This meets the baseline of 3 where schema does the heavy lifting.

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 'Get notion export result' clearly indicates the action (get) and the resource (notion export result), but 'export result' is vague and could refer to a status, a file, or a report. There are no siblings to differentiate from, so it lacks specific scope. It is not a tautology, but it lacks detail.

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 provides no guidance on when to use this tool, prerequisites, or alternatives. It does not mention whether an export job must be initiated first, how to obtain an id, or any conditions for use. There are no sibling tools, but even basic context is absent.

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