convergeqa_critique_templates

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

With no annotations, the description carries the full burden. It only says 'List', implying a read-only operation, but does not explicitly confirm safety, mention side effects, rate limits, or authentication details beyond the schema. More context is needed for a safe tool.

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 concise sentence of 10 words, front-loaded with the core action. It earns its place without fluff, though it could be slightly more informative without losing conciseness.

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 the complexity (6 parameters, 50% coverage, no output schema, no annotations, many siblings), the description is minimal. It does not explain return format, behavior on errors, pagination, or how 'API-visible' relates to the configured credential. Inadequate for effective tool selection and invocation.

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 coverage is only 50% (3 of 6 parameters have descriptions in schema), yet the description adds no information about any parameter. It fails to compensate for the undocumented parameters (output, credential_kind, redact_private_urls) and adds no value beyond the schema.

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 clearly states the action ('List') and resource ('ConvergeQA templates'), and adds context with 'API-visible' and 'for the configured credential'. However, it does not explicitly differentiate from the sibling tool 'convergeqa_iterate_templates', though the name implies the distinction.

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 guidance is provided on when to use this tool vs alternatives (e.g., convergeqa_iterate_templates) or when not to use it. The agent must rely solely on the tool name to infer usage context.

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