Notion Import Setup

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with "Read-only." It adds value beyond the annotations by explicitly stating "Does not install or modify any packages," which clarifies that the tool avoids any side effects beyond reading, a useful detail for agents concerned about system changes.

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: two short sentences that front-load the core purpose. Every word earns its place, with no filler or redundancy. The structure is efficient and immediately understandable.

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 the tool's low complexity (no parameters, no output schema, read-only annotations), the description is fully sufficient. It explains what the tool does, emphasizes its non-invasive nature, and the sibling list clarifies how it differs from `vault_import_notion`. No additional context is needed for an agent to invoke it correctly.

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 tool has no parameters, so schema description coverage is 100% by default. The description does not need to explain parameter meanings, and the baseline of 4 is appropriate for a zero-parameter tool since no additional semantic guidance is required.

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 the tool's function: "Report Notion import readiness and how to enable it." This specifies a verb (report) and a resource (Notion import readiness), and it distinguishes this tool from the sibling `vault_import_notion`, which actually performs the import.

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 implies usage as a preflight diagnostic by noting "Read-only" and "Does not install or modify any packages," which strongly suggests it should be used before the actual import. However, it does not explicitly name alternatives or state when not to use it, leaving the guidance somewhat implied rather than explicit.

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