alterios_patch_report_template

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

With no annotations, the description must fully disclose behavior. It states the scope (template only, preserve metadata) but does not explain if the operation is destructive, requires authentication, side effects (e.g., validation of template), or the role of dry_run. Incomplete transparency.

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?

Description is a single sentence, front-loaded with key action and scope, no redundant text. Efficient and easily parsed.

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?

Despite an output schema being present, the description does not reference it or explain return values. With 8 parameters and no schema descriptions, the description is far too sparse to cover the tool's complexity. The agent lacks context to use it correctly.

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 description adds no explanation for any of the 8 parameters (e.g., dry_run, expected_name, expected_marker). Agent must infer meaning from names alone, which is insufficient for correct invocation.

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?

Description clearly states the tool 'plan or replace only a report template while preserving report metadata.' It uses specific verb-resource pair and distinguishes from sibling tools like 'alterios_upsert_report' which likely handles full reports.

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 explicit guidance on when to use this tool versus alternatives. It implies template-only operations but does not mention scenarios where other tools (e.g., alterios_upsert_report) would be more appropriate. Lacks 'when not to use' or conditional context.

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