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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description usefully adds what each entry contains (approval requirement, read-only flag, snippet), but says nothing about pagination behaviour or result limits despite limit/offset parameters.

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 sentences, both front-loaded and load-bearing: the first defines the payload, the second gives the narrowing heuristic. No filler.

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 values need not be documented, yet the description helpfully enumerates the returned fields anyway. Combined with full schema coverage, an agent has enough to call this correctly; only pagination expectations are left to the schema.

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%, so every parameter (namespace, search, limit, offset) is already documented in the schema, establishing the baseline of 3. The description only restates the search-narrowing idea and adds no format or syntax detail beyond it.

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 one namespace's functions') and goes further by naming the fields returned: callable name, parameters, read-only flag, approval need, and a run_script-ready snippet. It is clearly distinct from list_integrations (which yields namespaces) and connects to run_script, though the sibling differentiation is implied rather than stated.

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 closing line 'crevioApi has hundreds of operations: narrow it with `search`' gives practical guidance, but it never states when to reach for this tool over list_integrations or search-type siblings, nor any prerequisites. Usage is implied (discover callable functions before invoking run_script) rather than explicit.

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