edubase_post_filebin_upload

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

Beyond the annotations, the description reveals important behavior: a previous valid link is returned unless force is set, and the response includes expiration and maximum file size. This helps an agent understand reuse semantics and the effect of the force parameter. No contradiction with readOnlyHint=false or other annotations.

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 three sentences with no filler: purpose, return values, workflow, and caching behavior are all included efficiently. It is compact while providing actionable guidance, and the most important action is stated first.

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 two-parameter tool with a rich output schema, the description covers all necessary operational context: what to do before calling, what to do after, how to use the returned identifier, and the effect of force. The mention of the sibling edubase_filebin completes the end-to-end workflow an agent needs.

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 already provides 100% description coverage for both parameters, including the enum for type and a clear explanation of force. The description reinforces the force behavior by explaining caching of a previous link, but does not add substantial new parameter-specific meaning beyond the schema.

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 clearly states it 'Generate[s] an upload link for the temporary file storage (filebin)' and lists the returned values (identifier, link, expiration, max file size). It distinguishes itself from the sibling edubase_filebin (which uploads the file) and edubase_delete_filebin_upload (which deletes an upload), so an agent can easily tell them apart.

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 gives a clear workflow: generate the link first, upload the file with edubase_filebin, then reference the filebin identifier in file-accepting fields. It implies when this tool is used without explicitly stating exclusions or alternatives, but the sequencing is concrete enough for an agent to invoke it correctly.

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