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

With no output schema, the sentence describing the return payload (JSON:API data, attributes, relationships, pagination metadata) is genuinely valuable context the agent could not otherwise know. 'Read-only' and the GET path largely restate the readOnlyHint annotation, and nothing is said about auth scope or rate limits, so it stops short of a 5.

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?

Three short sentences, front-loaded with purpose and followed by return shape then the endpoint. 'Read-only.' duplicates the readOnlyHint annotation and the GET path is redundant with the endpoint, so there is a little waste but no structural problem.

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 3-parameter list tool with a nested filters object and no output schema, the description covers purpose and return shape adequately while the schema carries full parameter detail. Missing only explicit guidance on filter usage and result volume.

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 100% and the schema itself documents page, page_size (1–100, default 20) and filters with concrete examples per resource. The description adds no parameter meaning of its own, so the baseline 3 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 specific verb and resource ('List the connected TOConline company's services') and names the endpoint GET /api/services. The resource noun 'services' distinguishes it from the many sibling list_* tools (products, customers, suppliers), though it never says so explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as toconline_list_products or toconline_list_item_families, and no advice on when pagination or filters matter. Usage is only inferable from the tool name.

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