edubase_get_organizations

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds the 'owned and managed' scope, but does not disclose behavioral nuances like rate limits, result ordering, or that the 'page' parameter is ignored in search mode (which is documented only in 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 extremely concise (5 words) with no extraneous content. Every word is meaningful and front-loaded, earning a top score.

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 tool has a clear purpose, an output schema, and annotations covering safety, the description is mostly complete. It could briefly mention pagination/filtering, but the schema handles that, so the description is adequate for a simple list tool.

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%, so the schema already describes each parameter well. The tool description adds no additional meaning beyond what is in the schema, thus meeting the baseline of 3.

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 'List owned and managed organizations' clearly identifies the tool's action (list) and scope (owned and managed organizations), distinguishing it from singular or other entity list tools. However, it omits mention of filtering and pagination capabilities, which slightly reduces clarity.

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 provides context on what organizations are returned (owned and managed) but offers no explicit guidance on when to use this tool versus alternatives (e.g., edubase_get_organization for a single record). There is no mention of parameter usage or pagination behavior.

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