List CKAN Organizations

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

Annotations declare readOnlyHint and idempotentHint, so the description does not need to restate safety. It adds value by disclosing pagination behavior, the special case where limit=0 returns only a count, and the output format options. This goes beyond what annotations provide, though it could mention error conditions.

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: a single sentence followed by a bullet list and a one-line workflow. Every sentence serves a purpose, and the structure is front-loaded with the core action. No wasted words.

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?

For a list tool with no output schema, the description covers return type, pagination, the count special case, and output format. The typical workflow provides broader context. It is nearly complete, though it could be more explicit about the fields in the returned objects when all_fields=true.

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% with detailed parameter descriptions. The description repeats parameter defaults and options in a bullet list but does not add significant new meaning beyond the schema. It provides a typical workflow that contextually ties parameters together, but for individual parameters, it adds little new.

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 title 'List CKAN Organizations' and description 'List all organizations on a CKAN server' clearly state the verb and resource. The included typical workflow distinguishes it from siblings like ckan_organization_search or ckan_organization_show, making the purpose unambiguous and well-differentiated.

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 does not explicitly state when to use this tool versus alternatives. The typical workflow hints at its role (list all → show one → search datasets), but there is no explicit guidance on when not to use it or when to prefer ckan_organization_search for filtered results.

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