edubase_patch_organization

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

Annotations indicate it is a write operation (readOnlyHint false) but not destructive (destructiveHint false). The description adds no further behavioral details, such as whether the update is partial or full, what happens if the organization doesn't exist, or any side effects.

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 short (one sentence) but lacks essential information about the update operation. It is under-specified rather than concisely informative.

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 presence of sibling tools for organization CRUD operations, the description should explain how this patch differs, what fields can be updated, and whether it supports partial updates. The output schema is missing, and the description does not cover return values or error cases.

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?

The input schema has one parameter 'organization' with a description, but the description 'Update organization.' does not explain that this parameter is the identifier for the target organization. Moreover, for a patch operation, one would expect additional parameters for fields to update, which are absent from the schema. The description fails to clarify the expected payload.

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 'Update organization.' clearly states the verb 'update' and resource 'organization', distinguishing it from create and delete siblings. However, it does not clarify what specific fields or operations are performed during the update, leaving ambiguity about the tool's exact purpose.

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 no guidance on when to use this tool versus alternatives like edubase_post_organization (create) or edubase_delete_organization (delete). It lacks context about prerequisites, required permissions, or typical scenarios.

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