ldap_auth_api_v1_auths_ldap_post

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

No annotations exist, so the description bears full responsibility. It only says 'Ldap Auth', disclosing nothing about side effects (e.g., session creation), success/failure outcomes, or required permissions.

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 concise at two words, but this results in under-specification. While conciseness is positive, the lack of structure and detail harms usability.

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?

For an authentication tool with no annotations and a simple schema, the description fails to cover context like return values (output schema exists but not described), error cases, or state changes. It is completely inadequate.

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 coverage is 0%, and the description adds no parameter details. The parameter names 'user' and 'password' are somewhat self-explanatory, but the tool does not clarify if 'user' is a username or email, nor any formatting constraints.

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 'Ldap Auth' indicates an LDAP authentication operation, but it is vague and does not specify the exact action (e.g., authenticate, login). It fails to differentiate from sibling auth tools like signin or get_session_user.

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 usage guidelines are provided. The agent receives no information about when to use this tool versus alternatives such as signin or other auth endpoints.

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