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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context by noting that each call returns one page and that summarize.all_pages aggregates over every page, though it does not discuss auth, rate limits, or filtering behavior.

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 brief and front-loaded, with the purpose first and the pagination caveat immediately after. Every sentence contributes useful information without redundancy.

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?

Given the output schema and annotation coverage, the description supplies the most important non-obvious operational detail: one page per call and how to get totals across pages. It is not exhaustive about filters and sorting, but the schema covers those areas adequately.

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 70%, so the schema already documents many parameters. The description adds meaning for pagination and summarize.all_pages, but it leaves most of the 10 parameters (limit, offset, expand, fields, sortby, sortorder, and filters) to the schema without further clarification.

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 states a specific verb and resource: retrieve a list of projects. It also identifies the underlying Fortnox API endpoint, but it does not explicitly differentiate this tool from sibling listing tools or project-related reporting tools.

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 useful pagination guidance ('One page per call') and points to summarize.all_pages for cross-page totals. However, it does not explicitly say when to use this tool instead of related project or reporting tools, so usage is mostly implied by the resource name.

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