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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: it describes the return shape (child names with child counts, parent path) and explains the round-trip performance difference between a single combined call and 1 + N calls. It does not cover error handling, permissions, or size limits, but for a read-only tool with annotations this is solid added context.

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 front-loaded with the core purpose, then usage context, then the advanced combined-call pattern. Every sentence contributes something useful: the return shape, the relationship to describe_database, the single-round-trip optimization, the alternative cost, and the final recommendation. It is appropriately sized for a tool with this much behavioral nuance.

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?

There is no output schema, so the description must carry the burden of explaining return values; it does so by stating child names, child counts, and parent path, and by describing what the combined call returns (note bodies). It also covers the primary usage flow and the performance trade-off, leaving no critical gap for an agent to call the tool 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?

Schema description coverage is 100%, so the schema already documents every parameter. The description adds meaning beyond the schema by explaining the interaction between depth and attributes (passing them together pulls a whole topic plus note bodies in one round-trip) and gives a concrete example (depth=2, attributes=["AI TEXT"]). It does not explain business or setName beyond the schema, but the key combined-parameter behavior is well covered.

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 states a specific verb and resource: 'Drill into a named set: returns its child names with child counts, plus the parent path.' It distinguishes itself from sibling tools by naming describe_database as a predecessor and describe_query as the alternative for per-child reads, so an agent can tell what this tool does and does not do without opening the schema.

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?

It explicitly says to use it after describe_database to explore a specific set, and it names describe_query as the alternative when depth/attributes are not passed. The guidance goes further by explaining the combined depth+attributes pattern for topic reads and instructing to 'Prefer the combined call for any topic-read,' giving clear when-to-use and when-not-to-use conditions.

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