ifcx_validate_viewer_compatibility

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

No behavioral traits disclosed. No annotations are provided, and the description only says it's an alias, offering no insight into effects, permissions, or side effects.

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 very short, but it is under-specified and provides no useful information. Conciseness alone is not beneficial when the content does not help the agent understand the tool.

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 three parameters and no annotations or output schema, the description is completely inadequate. It fails to provide essential context for a tool with multiple parameters and no other documentation.

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 has three parameters with 0% description coverage. The description does not add any meaning to the parameters, leaving the agent with no guidance on their purpose or usage.

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 it is an alias for another tool but does not explain what the tool actually does. The name suggests viewer compatibility validation, but the description only references an alias without specifying the function.

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. It being an alias suggests legacy use, but no explicit when/when-not instructions are provided.

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