api_get

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

With no annotations provided, the description carries the burden and does add real behavioral context: userId is injected automatically when absent, and status plus body are returned regardless of outcome so 404/400 are still informative. It does not mention authentication requirements, rate limits, or whether the raw call can be truncated, but for a passthrough GET wrapper the disclosure is substantial.

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: purpose and intended usage first, then per-parameter meaning and return behavior. Every clause carries information, and the example path is front-loaded for quick scanning.

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, so return structure need not be restated, and the description still usefully notes that errors return status+body. The main completeness gap is the absence of any contrast with the nearly identical sibling web_api_get, which matters for a raw-passthrough tool in a family of API wrappers.

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 0%, so the description must compensate, and it does: path is given a concrete example and params_json is explained as a JSON object of query parameters with an implicit userId injected when unset. That is meaningful semantics beyond the bare "string" schema, though the JSON encoding/escaping of params_json is not spelled out.

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: a raw GET against the parent API, explicitly framed for probing/discovering new endpoints, with a concrete path example ("/api/children"). It is clear on its own, but it never distinguishes itself from the sibling web_api_get, which appears to do something very similar.

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 phrase "for kartlegging av nye endepunkter" gives an implied use case (endpoint exploration rather than routine data fetching). However, there is no explicit when-to-use/when-not, no prerequisites, and no naming of the alternative web_api_get, leaving the agent to guess which of the two GET wrappers to pick.

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