Get annual aggregate turnover (AATO)

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

There are no annotations, so the description carries the disclosure burden. It states that this is a fetch operation and requires an active taxpayer session, which is useful. However, it does not describe the return structure, which turnover periods are included, or the exact data shape returned, leaving some behavioral ambiguity.

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?

The description is two short sentences with no filler. The core action and resource are front-loaded, and the authentication requirement is stated plainly in the second sentence.

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 parameterless getter, the description covers the essential information: what is fetched, whose data it is, and the session requirement. It does not detail the return format, but given the simplicity of the call and absence of an output schema, the remaining gap is minor.

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 has zero parameters, which warrants the baseline of 4. The description reinforces that no parameters are needed because the data belongs to the authenticated taxpayer.

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 specifies an exact verb ('Fetch'), resource ('Annual Aggregate Turnover values'), and scope ('authenticated taxpayer'). It is clearly distinct from the sibling tools, none of which target turnover values.

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 description gives a clear prerequisite—an active taxpayer session—which helps the agent know when the tool is callable. However, it does not explicitly discuss when to prefer this tool over alternatives or when not to use it; usage is mostly implied by the tool's purpose.

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