edubase_patch_organization_job

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds genuinely useful context beyond that: members retain the job role and its competencies, so the agent knows the update does not cascade. It still omits partial-update behavior (what happens if neither title nor id is sent) and the empty-string removal semantics.

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?

Two short sentences with the mutable fields front-loaded and the non-destructive consequence immediately after. Nothing is redundant or padded.

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 4-parameter mutation with full schema coverage and no output schema, the description covers what changes and the key non-side-effect. However, it leaves out partial-update semantics and the "empty string removes the external id" case, which matter for calling a PATCH tool correctly.

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 title, id, job, and organization are all documented in the schema. The description only restates that name/title and external identifier/id are the mutable fields; it adds no detail on the ambiguity that title and id are optional in a required-organization+job PATCH, which is exactly where extra meaning would help.

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?

"Update the name or the external identifier of a job role in an organization" gives a specific verb plus resource and even names the two mutable fields, so the agent can distinguish it from the create/get/delete job siblings. It does not explicitly reference those siblings, but the PATCH scope is unambiguous.

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?

There is no statement of when to use this instead of edubase_post_organization_job, edubase_get_organization_job, or edubase_delete_organization_job, and no prerequisites (e.g. that the role must already exist). The second sentence describes a side effect, not a usage condition.

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