edubase_get_organization_jobs

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds a genuine behavioral detail — results are ordered by name — but says nothing about pagination, result size, or what happens if the organization has no roles.

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 first sentence is front-loaded and precise. The second sentence about competencies is domain context rather than invocation guidance, but it is short and not harmful.

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?

An output schema exists, so return shape need not be explained, and ordering plus scope are stated. For a single-parameter read tool this is close to complete; pagination behavior is the only meaningful omission.

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?

Only one parameter and schema coverage is 100%, so the schema already documents it. The description adds nothing about the format of the organization identifier (id vs slug), leaving a real ambiguity unaddressed; baseline 3 applies.

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?

States a specific verb and resource ("List all job roles in an organization") plus ordering, which distinguishes it from the singular sibling edubase_get_organization_job in intent. It stops short of naming that sibling explicitly, so an agent must infer the list-vs-fetch distinction.

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?

Usage is implied by "List all" — you call it to enumerate job roles before assigning competencies or picking a role id. There is no explicit when-to-use/when-not guidance and no mention of the alternatives among siblings (e.g. the singular get, or the post/patch/delete job endpoints).

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