tdarr_public_auth_login

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

No annotations are provided, so the description carries full burden. It indicates a mutation (logging in) but does not disclose side effects like setting a session, returning tokens, or error conditions. The behavioral implications are under-described for a secure authentication operation.

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 extremely concise with a single sentence that conveys the core purpose. No wasted words, but it lacks structure or front-loading of key information, which is acceptable for a straightforward 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 absence of annotations and output schema, the description should explain what happens after login (e.g., token returned, session active). It covers the basic action but fails to specify the outcome or side effects, leaving the agent without the full picture for a security-critical operation.

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% with clear attribute names and descriptions ('Username', 'Password'). The tool description adds no additional semantics beyond the schema, meeting the baseline for high coverage. No parameter-level details are provided in the description.

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 clearly states the verb 'Log in' and the resource 'a user', which is specific and distinguishes from sibling tools like 'tdarr_public_auth_register' or 'tdarr_auth_logout'. However, it doesn't specify what logging in entails (e.g., returning a token), which could be slightly ambiguous.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no context about authentication state or required permissions. The description simply states the action without any usage context.

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