Get Neo4j Schema & Indexes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about sample_size affecting speed/accuracy and warns about token limits from large properties, going beyond the annotations. No contradiction found.

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 main purpose is front-loaded, followed by a bulleted breakdown and a concrete example. It is moderately concise and well-structured, though slightly verbose with some redundancy between the bullet points and the follow-up example.

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?

Even without an output schema, the description conveys the key outputs (indexes, schemas, warnings) and explains why they matter. It gives enough context for an agent to understand when to call it, what to expect, and how to use sample_size effectively.

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 schema already provides complete coverage of sample_size with a description of its effect on speed and accuracy. The description adds guidance on when to provide it (only if requested by user or for performance tuning), which is extra value 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 clearly states the tool returns Neo4j graph schema with search indexes and property size warnings. It uses a specific verb ('Returns') and resource ('Neo4j graph schema'), and distinguishes itself from sibling search tools by positioning itself as a prerequisite step.

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?

Explicitly instructs to call this tool BEFORE using vector_search, fulltext_search, or search_cypher_query, providing clear when-to-use guidance. It also explains how property size warnings help choose return_properties, reinforcing practical usage context.

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