Export governed CSV

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

The description aligns with annotations (readOnlyHint=true, destructiveHint=false) and adds context about the authentication method (x-api-key M2M) and endpoint. However, it does not disclose additional behavioral traits such as response format, size limits, or error handling beyond what annotations already provide.

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?

The description is a single sentence with no wasted words, and the 'READ role:' prefix is front-loaded. However, it could be more structurally organized (e.g., separate usage notes from technical details).

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 only one parameter and no output schema, the description provides the endpoint and auth method but omits critical details: the output format (CSV), success/error responses, prerequisites (e.g., listing domains first), and typical usage context. This leaves the agent underinformed.

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?

The schema has 0% description coverage for the single required parameter 'domain'. The description does not elaborate on the parameter's meaning, constraints, or format beyond the endpoint path hint. Since coverage is low, the description should compensate, but it fails to do so.

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 clearly states the verb 'export' and resource 'iGrid domain', and specifies the HTTP method and endpoint. However, it does not explicitly distinguish from sibling tools like igrid_ingest_csv (import) or igrid_list_domains, and the title mentions 'CSV' but the description omits the output format.

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?

No guidance is provided on when to use this tool versus alternatives. The 'READ role' prefix hints at read-only usage, but there is no explicit comparison to siblings or conditions for use.

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