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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned fields (name, type, website, parent, children, domain status, metadata) and confirming depth-independent behavior. Missing only failure behavior for an invalid slug.

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?

Two sentences, no filler. The core action and the key identifier come first, supporting examples follow. Every clause carries information.

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?

With a single required parameter and no output schema, the description covers the essentials by listing return fields and the breadth of the hierarchy. It falls short only on edge cases (invalid/unknown slug behavior) and on routing guidance against sibling lookup tools.

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 coverage is 100% and the slug parameter's own description already gives examples and says 'at any depth'. The description reinforces the depth flexibility and adds a deeper nesting example, but adds no syntax rules beyond the schema. Baseline 3 applies when the 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?

States a specific verb+resource ('Get full details for a specific government entity') keyed on a URL slug, and names the entity types covered (cities, school districts, special districts). It is clearly distinguishable from sibling search/list tools like search_entities and list_countries.

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?

Usage is implied rather than stated: the tool requires an exact URL slug, and the description shows two example slugs, which hints that you need the identifier already. However, it never explicitly says when to use this versus search_entities or resolve_jurisdiction when you only have a name or domain.

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