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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the crucial behavior that the tool 'opens nothing by itself' and returns step-by-step screens/buttons/fields, which prevents an agent from expecting direct data retrieval. It could clarify the meaning of 'Exact Online's official API: Yes', but the key behavioral traits are disclosed.

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 short but not tightly front-loaded: the key clarification that it returns instructions appears in the second sentence, and phrases like 'from ChatGPT, Claude or any AI agent' and the fragment 'Exact Online's official API: Yes' add little or unclear value.

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 guide tool with no output schema, it adequately explains that the return is a step-by-step procedure and that execution requires browser tools. However, it does not define what counts as 'outstanding items' or clarify the cryptic API note, leaving domain intent partially underspecified.

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 are zero parameters and schema description coverage is 100%, so the schema carries no burden and the description does not need to explain parameter semantics. The baseline for zero-param tools is 4.

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 name and opening clause say 'List outstanding items', but the description then says it 'Returns how to do it... step by step', so the actual function is a procedural guide rather than a data lister. It does specify the resource (Exact Online account) and the follow-up tools, but the initial mismatch weakens clarity.

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?

It implies you should use this when you need to handle outstanding items and explicitly points to cotlet_browser_* tools for execution, but it never states when to choose this over exact_online_book_journal_entry or other siblings, nor when not to use it.

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