alterios_diagnose_report_viewer

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

No annotations provided, so the description bears full responsibility. It only says 'diagnose separately' without disclosing whether the tool is read-only, what it returns, or side effects. This is insufficient for an AI agent to infer safe usage.

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 sentence, which is concise but lacks structure. It does not use bullet points or sections to organize information about the tool's behavior. It is minimal yet unhelpful for a complex tool with many parameters.

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 the tool having 13 parameters and an output schema, the description provides no context about return values, what 'diagnosing separately' entails, or how to interpret results. It fails to cover essential aspects for effective use.

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 the description adds no explanations for any of the 13 parameters (e.g., form_id, sample_rows, expected_mode). The agent has no information to correctly fill parameters beyond their names and types.

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 states 'Diagnose report data, template, form binding, PDF, and browser viewer evidence separately.' This vaguely indicates the tool examines different report components, but the verb 'Diagnose' is unclear and does not specify the output or action. It fails to distinguish from siblings like 'alterios_report_full' or 'alterios_validate_printable_render'.

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 on when to use this tool versus alternatives. The description does not mention context, prerequisites, or conditions. With many sibling tools, lack of differentiation is a significant gap.

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