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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=false) it discloses output typing ('cells stay strings'), input support ('quoted fields'), the auth scoping requirement, and a concrete attemptId/retry policy. Some of this overlaps annotation-declared traits (determinism, no external fetch), so it is strong but not fully additive.

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?

Four short sentences, purpose front-loaded, each carrying a distinct fact (format, computation model, auth, retry). Slightly telegraphic in places but 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?

With no output schema and a nested input object, the description only gestures at the return shape ('cells stay strings') without saying how rows map to objects or how headers are used. Prerequisites and retry semantics are complete, but the output contract remains underspecified.

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 only 50% and the csv field carries no schema description, so the description's notes on cell typing and quoted-field support meaningfully compensate for that gap. It also reinforces the attemptId contract beyond the schema's own text, though it does not state size limits or header handling.

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?

The description states a specific operation on a specific resource: built-in CSV-to-JSON conversion, with the title/name fixing the direction. It is clear what the tool does, but it never names the reverse sibling (invokeport_json_csv) to make the direction unambiguous from the text alone.

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 real operating context: free deterministic computation, no LLM or external fetch, a scoped key permitting csv-json, and an explicit retry policy for uncertain outcomes. It stops short of stating when to choose this over the sibling converters, so it is clear context rather than full when/when-not routing.

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