get_translation_help

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

The description tells the agent what the operation returns — help text and usage examples — and thus describes the complete observable behavior. Since there are no annotations and no realistic side effects for a help lookup, the description carries the transparency burden reasonably well.

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?

Two sentences, no fluff, and a clear 'Returns:' marker makes it easy to scan. Every word earns its place.

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 zero parameters and an output schema, the description is nearly complete for a help-intent tool. It states what the user receives and covering the full scope of the operation; a little more explicit context about which translator features the help covers would fully set expectations.

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 tool has zero parameters, so there is no schema to reinforce or undocumented input to compensate for. The baseline of 4 applies because the description has nothing to add about non-existent parameters and no semantic risk to mitigate.

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 clear verb and resource: get help about using the PowerPoint translator. The mention of 'help text and usage examples' makes its purpose concrete and distinct from translation/export sibling tools.

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 name and description imply that this should be used when an agent needs assistance or examples about the translator. However, there is no explicit 'when to use this vs alternatives' statement, though the absence is less harmful here because siblings are task-execution tools and this is clearly the help lookup tool.

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