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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real context beyond them: 'source-validated' (data provenance/freshness) and 'no account required' (auth profile). It does not mention caching or rate behavior, but that is minor for a zero-param read.

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 clipped sentences, front-loaded with the resource and followed by the cost/auth fact. No filler.

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 zero-parameter, read-only, open-world lookup with no output schema, the description covers purpose plus the key cost/auth facts an agent needs before calling. Its only gap is routing relative to compare_ndis_sda, which the description ignores.

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?

The tool takes no parameters, so the schema has nothing to document and there is no parameter semantic burden to compensate for. Baseline 4 applies.

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 clear verb ('Get') and a specific resource ('SDA building, design and SA4 choices'), and 'source-validated' signals data quality. It is distinguishable from the sibling compare_ndis_sda, though the SDA-domain jargon ('SA4 choices') keeps it from being fully self-explanatory.

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?

The only usage context is a precondition ('Free; no account required'). There is no statement of when to call this vs. compare_ndis_sda, which is the obvious sibling, and no indication of what the agent should do with the result.

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