ethora-app-list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the login requirement (useful context), but doesn't describe what the tool returns (list format, pagination, error behavior) or any other behavioral traits like rate limits or authentication specifics. For a tool with zero annotation coverage, this is insufficient.

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 (two short phrases) with zero wasted words. It's appropriately sized for a simple list tool, though it could be slightly more informative. The structure is straightforward with the main action stated first.

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 no annotations and no output schema, the description is incomplete. It mentions the login requirement but doesn't explain what the tool returns (application list format, fields included) or any other contextual details needed for proper use. For a tool in a family with multiple application-related tools, more context is needed.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description doesn't need to compensate for any parameter gaps. Baseline is 4 for zero-parameter tools as the description doesn't have to explain parameters.

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 the action ('List application') which is a clear verb, but it's vague about what exactly is being listed (applications in general? user's applications?). It doesn't distinguish from siblings like 'ethora-app-get-default-rooms' which also retrieves application-related data. The purpose is understandable but lacks specificity.

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 includes a prerequisite ('user should login first') which provides some context, but offers no guidance on when to use this tool versus alternatives like 'ethora-app-create' or 'ethora-app-get-default-rooms'. There's no explicit when/when-not usage or comparison to sibling tools.

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