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

Goes well beyond the readOnlyHint annotation by disclosing pagination mechanics (collection responses carry {data, has_more}, next page via starting_after with the last returned id, same filters), default page size 10 and max 100. It also states what is never returned (GPS and location curves) and how the fields param trims payloads, which is exactly the operational detail annotations cannot convey.

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?

Front-loaded with purpose and usage rule, then layered detail on path, params, pagination, fields and exclusions. It is dense but nearly every sentence carries operational information; the example lists are slightly long but they substitute for the missing schema descriptions.

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?

An output schema exists, yet the description still notes the envelope shape ({data, has_more}) because callers must act on it for pagination. Combined with the path format, param examples, page-size limits and excluded data categories, an agent has everything needed to call a generic open-ended endpoint correctly.

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 0%, so the description carries the full burden and does so convincingly: `path` must be a v2 path without the /api/v2 prefix, with four concrete examples, and `params` are query params illustrated with date_from/date_to/limit plus the cursor and fields cases. This turns two undocumented free-form parameters into something an agent can use correctly on the first try.

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: 'Read any Nolio API v2 GET endpoint.' It immediately delimits scope ('GET endpoint', 'no curated read tool fits'), which cleanly separates it from nolio_api_write and the curated read tools like get_records or get_calendar.

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 gives a clear selection rule: use this when no curated read tool fits. That is genuine routing guidance rather than inference. However, it does not name the closely related helpers get_endpoint_schema or search_nolio_api_docs, which an agent would need to discover the correct path — the natural next-step alternatives go unmentioned.

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