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

Annotations already declare readOnly, idempotent, non-destructive and closedWorld, so safety is covered. The description adds genuinely new behaviour: the response bundles three assessment dimensions plus the court AI rules in one call, and an unrecognised tool is not an error but returns a not_recorded status — a fallback an agent must know about to interpret results correctly.

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 output content is front-loaded in the first sentence and the non-obvious fallback behaviour is placed last where it stands out. 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 no output schema, the description carries the burden of indicating what comes back, and it does so only at a high level ("adoption, efficiency and governance" plus rules) without mention of shape or scoring method. It also does not note that jurisdiction will be prompted for if omitted, leaving the schema's 51-value forum enum and jurisdiction handling uncontextualised in prose.

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 explains task, tool, forum and jurisdiction, including the instruction to omit jurisdiction to be asked. The description reinforces the key semantic constraint — exactly one tool on exactly one task — but adds no format guidance for the tool identifier (name versus catalogue profile id) beyond what the schema states.

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 uses a concrete verb ("Returns") and names specific resources: catalogue adoption, efficiency and governance for one tool on one task, plus the matching court AI rules. That is clearly distinct from a plain profile lookup like get_software_profile or a pure rules lookup like find_rules, though it never names those siblings explicitly to sharpen the boundary.

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 statement of when to reach for this tool versus get_software_profile (raw profile), find_rules (rules only) or disclosure_duties. Usage is only inferable from the purpose sentence. The one piece of routing information given — that unlisted tools stay not_recorded — is about behaviour, not about when to call it.

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