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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the 'Read-only; takes no parameters' line adds little, but the description goes further by disclosing the return shape inline and the key constraint that presentations cannot otherwise be created without an upload. That is real behavioral context beyond the 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?

Front-loads the purpose in one sentence, then a definitional paragraph, then a bolded Returns block and next-step pointer. Every sentence carries information an agent needs to decide or act; nothing is redundant with the name.

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?

There is no output schema, and the description compensates by spelling out the return object and the field names (id, name, description, artifactType, framework?). Combined with the follow-up call instruction, an agent can invoke this and use the result without any other source.

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?

Zero parameters, so the baseline is 4; the description confirms 'takes no parameters' consistently with the empty schema. There is nothing further to disambiguate, though it also does not need to.

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 ('List the templates a NEW artifact can start from') and instantly separates itself from artifact-create_from_template by noting templates are inputs to creation, not the creation itself. The concept of a template is defined concretely with examples.

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?

Explicitly says when to prefer a template ('faster and more reliable than writing the project from scratch') and gives a hard requirement case ('the only way to create a presentation without uploading a presentation file'). It also routes the agent forward with 'Pass the chosen id to artifact-create_from_template.'

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