exporter_anki

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool builds a deck from local course cards but omits prerequisites, side effects, where the generated file goes, whether the course must already exist, or any authentication requirements.

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 a single front-loaded sentence with no wasted words. However, it is extremely sparse for a tool that requires prerequisites and parameter context, making it feel under-specified rather than optimally concise.

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?

An output schema exists, so return values needn't be explained, but with no annotations and zero schema coverage the description must carry more weight. It does not explain prerequisites, the meaning of 'cours', or when calling the tool is appropriate, leaving the agent with significant gaps.

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%, and the single parameter 'cours' has no schema-level description. The description adds only that it refers to a 'cours local' (local course), but does not clarify the expected value, format, or whether it must match an existing course identifier.

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 ('Construit') and resource ('le deck Anki (.apkg)') plus the source ('à partir des cartes du cours local'). It distinguishes itself from siblings like 'telecharger_fichier' or 'cartes' by naming the Anki format, though it doesn't explicitly contrast with alternatives.

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?

No when-to-use or when-not-to-use guidance is provided. The description implies the tool is for exporting Anki decks but does not mention prerequisites or alternatives among the sibling tools such as 'telecharger_fichier' or 'cartes'.

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