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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds one genuinely useful behavioural detail — that court AI rules are conditionally attached when a jurisdiction code is supplied — but says nothing about what happens with an unrecognised area, whether unpublished areas error, or what the prompt payload looks like.

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 short sentences, zero filler, with the core return value front-loaded and the conditional modifier second. Nothing could be removed without losing 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?

For a simple read-only getter with full annotations and complete enum coverage, the description adequately conveys both what is returned and the one conditional variation. The absence of an output schema is mostly mitigated by naming the two return components (prompt plus attached court AI rules).

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 50%: jurisdiction carries a rich description, while area has only an enum. Both parameters are enums and largely self-documenting, but the description adds no meaning about how the two interact (e.g. that jurisdiction augments rather than replaces the area prompt), so it does not compensate for the uncovered half.

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 and resource ('returns the published practice-area prompt for one Australian area'), which is distinguishable from siblings like get_framework, get_precedent and search_library. It does not explicitly contrast itself with the closer-sounding get_jurisdiction_guidance, so it stops short of full sibling differentiation.

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 or when-not-to-use guidance, and no alternative is named among the many legal-context siblings. The only conditional sentence ('Court AI rules are attached when a jurisdiction code is given') describes output behaviour rather than routing.

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