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

No annotations are provided, so the description carries the full behavioral burden. "Retrieve" implies a read, and the content categories are named, but nothing is said about what happens for an unknown or unsupported municipality, whether the statutory/geotechnical rules are versioned or jurisdiction-specific, or how current the data is.

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 with no filler; the retrieval verb and the content list come first. It is slightly dense in bundling four distinct content categories plus a jurisdiction scope, but no sentence is wasted.

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?

This is a simple one-parameter read tool with a fully documented schema and no output schema, and the description enumerates the content categories an agent will receive. It is close to complete; only unsupported-municipality and data-currency behavior are missing.

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?

There is a single parameter with 100% schema description coverage, including worked examples of full names and abbreviations, so the schema already does the explanatory work. The description adds no additional meaning about matching behavior (e.g. fuzzy matching or handling of unrecognised names), which is the baseline 3 case.

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 ("Retrieve") and enumerates the concrete resources returned: submission checklists, statutory Form 1/2, geotechnical/dolomite rules, and rejection delay factors, scoped to South African metropolitan municipalities. It is clear what the tool returns, but it does not differentiate itself from the sibling get_common_rejection_pitfalls, whose scope appears to overlap with the "rejection delay factors" content listed here.

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?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. The only implied usage is that an agent should call it when it needs municipal submission requirements, and the overlap with get_common_rejection_pitfalls is left unresolved rather than routed.

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