zenhub_get_owner_by_login

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

No annotations are provided, and the description does not disclose behavioral traits such as what happens if the login is not found, required permissions, or rate limits. For a lookup tool, basic behavior like error handling is missing, so the description falls short.

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 a single, short sentence (7 words) that conveys the essential purpose without any filler. It is highly concise and front-loaded, making it easy to parse quickly.

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 tool's simplicity (single parameter, no output schema), the description is minimally adequate. However, it lacks any mention of the return value or context like common use cases. With no annotations, slightly more context would be beneficial for completeness.

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 input schema covers 100% of parameters with a description for 'login'. The tool description adds no additional meaning beyond the schema, meeting the baseline expectation but not exceeding it. No extra semantics are provided.

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 uses a specific verb 'Lookup' and clearly identifies the resource as a 'GitHub user/organization' by 'login'. This distinguishes it from the sibling tool 'zenhub_get_owner_by_gh_id', which looks up by GitHub ID. The purpose is unambiguous.

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 does not explicitly state when to use this tool versus alternatives like zenhub_get_owner_by_gh_id. While the name implies login-based lookup, there is no direct guidance on when not to use it or which other tools are preferable for ID-based lookups. This is a moderate gap.

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