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

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: the data is quoted from the provider's own SLA and status pages, kept separate rather than merged, and APIs.io runs no monitors so nothing is measured or verified. It also explains that a 'generated' method marks a synthetic base with no uptime figure and is not a provider statement — exactly the provenance caveat an agent needs before trusting results.

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 identity and scope, then provenance caveat, then filtering and the alternative tool — a sensible order with no filler. Some sentences are compressed to the point of being cryptic ('kept separate, quoted from its own pages') and the filter/alternative guidance is tacked on as a run of clauses.

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 10-parameter, zero-required listing tool with no output schema, the description covers the important unknowns: source of the data, non-verification, what method="generated" means, and how to get full bodies. Pagination and sort behavior are left entirely to the schema, which is acceptable since it is fully described.

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%, so all ten parameters are already documented in the schema, including q, tags, providers, include, and the searched/generated values of method. The description largely restates those (filters, include=["content"], method semantics), adding little syntax or meaning the schema does not already carry.

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?

Opens with a specific resource and scope: 'Service levels (SLA4OAI) across the catalog', and explicitly routes the agent elsewhere with 'Use find_artifacts for cross-type search', which separates it from the large family of find_* siblings. The retrieval verb is only implied by 'Filter by q / tags / providers', so it is clear but not a clean verb+resource statement.

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?

Gives concrete usage: filter by q / tags / providers, and pass include=["content"] to inline bodies. It also names an explicit alternative (find_artifacts) for cross-type search. It stops short of stating when-not to use this tool beyond that single cross-type exclusion.

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