List Fortnox read endpoints

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds useful context on the return shape (path templates and summaries) but does not describe pagination, result size, or how to use the returned templates.

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 tight sentences with the purpose and return value front-loaded. Minor redundancy: 'read-only' restates the readOnlyHint annotation, but no meaningful waste otherwise.

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 simple one-parameter discovery tool, the description covers what it searches, what it returns, and which tool consumes the output, which is sufficient without an output schema. It could be slightly more explicit about how to chain into fortnox_get.

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 coverage is 100% and the single 'search' parameter is fully documented with examples in the schema. The description adds no syntax or matching-behavior detail beyond what the schema already provides, so baseline 3 is appropriate.

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 specific verb (search/list) and resource (the read-only Fortnox endpoints that fortnox_get can call), and gives concrete category examples. It clearly differentiates itself from the data-returning siblings by being a discovery tool for fortnox_get rather than a data list itself.

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?

By naming fortnox_get as the consumer, it implies this is the discovery step before calling that tool, but it never explicitly says when to use this versus a direct list_* sibling or how to proceed after finding an endpoint. Usage is implied rather than stated.

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