Show CKAN Group Details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds minimal extra behavioral context, only mentioning return format. With annotations covering the safety profile, the description doesn't need to repeat but could add more (e.g., auth requirements).

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 very concise: two sentences plus a typical workflow line. Every sentence adds value, and the purpose is front-loaded.

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 4 parameters, no output schema, but annotations cover safety, the description explains return format (markdown or json) and includes a workflow. It is fairly complete for a read tool, though could mention error handling or default behavior.

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 100%, so baseline is 3. The description restates parameter names and types but adds little beyond what the schema already provides (e.g., 'Group ID or name' vs schema description). No additional semantics or format details.

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 'Get details of a specific group', specifying the verb and resource. It distinguishes from sibling tools like ckan_group_list and ckan_group_search, which list or search groups.

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?

Provides a typical workflow (ckan_group_show → ckan_package_show → ckan_datastore_search), giving context for when to use this tool in a sequence. While it doesn't explicitly state when not to use, the workflow guidance is clear and helpful.

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