Get domain CSV template

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description appropriately adds that the template is 'contract-accurate', which is meaningful behavioral context beyond the annotations—it implies the returned CSV matches a predefined contract schema.

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, front-loaded sentence that efficiently conveys the verb, output, context (contract-accurate), and resource (iGrid domain). Every word earns its place with no redundancy.

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?

Given the low complexity (1 parameter, no output schema, simple return type), the description is mostly complete. It could mention whether the template is downloaded or returned as a string, but the phrase 'return the ... CSV template' implies the tool returns the template data.

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. It identifies the sole parameter 'domain' by stating 'for an iGrid domain'—this directly maps the parameter name to a meaningful concept (the iGrid domain). Though it doesn't elaborate on format, the mapping is clear and sufficient because there is only one required parameter.

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 uses the specific verb 'return' with the resource 'CSV template for an iGrid domain', and clarifies the result is 'contract-accurate'. It also distinguishes from sibling tools like igrid_export_csv and igrid_ingest_csv by naming the specific artifact type (template, not data export or ingestion).

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 description states the READ role requirement, implying authentication context, and the template name includes 'domain' which matches the sole required parameter. However, it does not explicitly state when an agent should use this tool versus alternatives like igrid_export_csv (to get template vs. export actual data) or igrid_ingest_csv (to import data).

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