tradify_type

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

No annotations are supplied, so the description carries the full behavioral burden and mostly fails to meet it. It says nothing about whether existing field contents are replaced or appended, whether typing triggers validation or auto-save, what happens if the field number is stale or out of range, or what a successful call returns.

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?

A single front-loaded sentence with no filler, and the target of the action is stated before any qualifiers. Nothing can be trimmed without losing meaning.

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?

This is a browser-automation mutation primitive with no annotations and no output schema, so the description must explain sequencing, side effects, and failure behavior — none of which it does. Given the complexity of driving a live page, the definition is too thin for an agent to call it confidently outside the happy path.

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 100%, so both parameters (text and element) are already documented, including that element comes 'from the last read'. The description adds only the framing of a 'numbered field on the current page', which is roughly equivalent to what the schema already conveys, making 3 the correct baseline.

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 gives a specific verb (type) and a specific target (a numbered field on the current Tradify page), which clearly separates it from siblings like tradify_click, tradify_read, and tradify_open. It stops short of naming any sibling explicitly, so it lands at a clear-but-undifferentiated 4.

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?

Usage is only implied: 'numbered field' and 'current page' suggest you must first open a page and read it to obtain a field number, but the description never states that prerequisite or when to prefer this over tradify_click. An agent can infer the workflow but is given no explicit when/when-not guidance.

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