validate_notion_connection

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this with "without modifying Notion" while adding genuine scope detail: it enumerates what is read (auth plus Database/Data Source/property schemas). It stops short of failure semantics — whether a bad token surfaces as an error, a status field, or partial results — which matters for a tool whose whole purpose is health-checking.

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?

A single front-loaded sentence that names the verb, the resources, and the safety constraint with no filler. Every clause carries information an agent can act on.

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?

An output schema exists, so return values needn't be described, and with no parameters there is no input burden — the description covers purpose and safety adequately. The remaining gap is that for a validation/smoke-test tool it doesn't indicate what a successful versus failed probe looks like at a high level, leaving that entirely to the output schema.

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 takes zero parameters, so per the baseline this starts at 4. Nothing in the description is needed to explain inputs, and nothing misleads about them.

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?

States a specific verb (Read) and enumerates the exact resources probed — authentication, Database, Data Source, and property schemas — which clearly separates it from write-side siblings like publish_to_notion and preview_notion_publication. The only friction is that the name says "validate connection" while the description frames the work as schema reading; the two are closely related but the description never explicitly ties the reads back to a connection verdict.

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 phrase "without modifying Notion" implies this is a pre-flight/safe-inspection step, but the description never says when to call it — e.g. before publish_to_notion or when publication status looks wrong — nor does it name an alternative. Usage has to be inferred from the context of the sibling set rather than read off the text.

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