list_web_apps

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

With no annotations provided, the description must disclose behavioral traits such as read-only nature, pagination, filtering, or sorting. The description only says 'List,' implying read-only but not explicitly, and fails to mention the presence of parameters like limit, offset, sort_by, or from_date that affect behavior.

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 brief (4 words), which is concise but under-specified. It lacks essential details such as parameter hints or usage context. While front-loaded, it sacrifices completeness for brevity, making it less helpful than a slightly longer but more informative description.

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 of 6 optional parameters and the presence of an output schema (not shown), the description is severely incomplete. It fails to convey that the tool supports pagination, filtering by tags/title/date, sorting, or the structure of the response. The agent lacks critical information to use the tool 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%, meaning no parameters are described in the schema. The description does not compensate by explaining any of the 6 parameters (tags, limit, title, offset, sort_by, from_date) or their semantics, leaving the agent with no information beyond parameter names.

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 explicitly states 'List AbleSign web apps,' which is a specific verb (List) and resource (AbleSign web apps). This clearly distinguishes it from sibling tools like list_workspaces, list_screens, etc., which list different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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