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

With no annotations, the description carries the full behavioral burden, yet 'Uses the same authorization and validation as website, API and CLI' is the only trait disclosed and it is left undefined. Nothing is said about what the export returns, whether it consumes quota, whether it is idempotent, or what happens on a missing/inaccessible artifact.

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 text is short, but its brevity comes from under-specification rather than economy; the opening clause is redundant with the tool name while the substantive clause is vague. No front-loaded statement of what the tool produces.

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-required-parameter tool with 0% parameter coverage, no annotations and no output schema, the description should explain the id/workspace pair and the export result. Instead it says only that auth and validation mirror other surfaces, leaving the agent unable to call the tool correctly with confidence.

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 0% for two required parameters (id, workspaceId), so the description must compensate and instead says nothing at all about them — not even that id identifies the artifact to export or that workspaceId scopes it. Agents get no disambiguation between the two UUID fields.

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?

"SAGOT artifacts.export" merely restates the tool name with a namespace prefix and never says what an export actually does — download a file, stream bytes, produce a URL, or return a job handle. The agent cannot tell artifacts_export apart from artifacts_delete or from the many other sibling export/list tools on the basis of this text.

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 when-to-use or when-not-to-use guidance and no named alternative among the ~100 siblings. The only contextual hint is that authorization/validation matches the website, API and CLI — useful for parity reasoning but not a usage rule.

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