Api task templates object retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered; the description adds nothing and instead frames the tool as an export mixin. No mention of what is fetched, whether missing ids error, or any permission/side-effect context.

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?

It is a single short sentence, so there's no bloat, but its brevity comes from being a leftover code docstring rather than a front-loaded statement of purpose. Being short does not help when the content is wrong.

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 retrieve-by-id tool with no output schema and an undocumented id parameter, the description should at minimum say it returns a task template. It provides nothing usable and points the agent toward an unrelated export concept.

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 single required parameter 'id' has 0% schema description coverage and the description never mentions it or what kind of identifier it expects. With no schema documentation, the description needed to carry this and does not.

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?

The description says 'Generic export mixin for CSV/XLSX exports', which describes an export mechanism, not the retrieval of a single task template object identified by id. It is actively misleading about what the tool does and offers no way to distinguish it from siblings like task_templates_export_csv_retrieve or task_templates_list.

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 statement of when to use this tool, when not to, or which sibling to prefer for listing, exporting, or updating task templates. An agent reading this would likely route to export-oriented calls instead of the object retrieve.

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