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

With no annotations present, the description carries the full burden; it does usefully disclose the zip packaging and that the download link expires in 15 minutes, which an agent cannot infer elsewhere. It is silent on permission requirements, whether exports are billed or size-limited, and whether repeated calls regenerate new links.

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?

A single front-loaded sentence that moves from action to contents to platforms to return value with no filler. The three-platform list makes it dense but each token carries information.

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?

It covers the return contract even without an output schema and names the export targets, but for a tool with a nested object parameter and organisation-scoped access it omits auth expectations and any constraint on combining source with target. Adequate rather than complete.

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 100%, so all four parameters are already documented, including enum meanings and the nested dataset shape. The description adds no parameter-level meaning beyond restating that practice variants bundle tasks and that a tool dataset may be included.

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 ("Exports an eval rubric") plus the artifact contents (practice tasks or an MCP server's tool dataset), the output format (zip), the three destination platforms, and the return value. An agent can distinguish it from export_policy_pack purely from the description.

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 only implied by the enumerated destination platforms; the description never says when to choose this over export_policy_pack or what preconditions must hold. The useful routing constraints ("Tool descriptions go to foundry only; agent sessions not to claude-outcomes") live in the schema, not the description.

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