login

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

Discloses key behavioral traits: 'Opens a browser for the user to log in, then saves the token automatically.' Since no annotations are provided, this covers important side effects.

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?

Three efficient sentences with front-loaded purpose. Every sentence adds value: purpose, usage context, and behavior. No extraneous words.

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 or output schema, the description covers purpose, when to use, behavior, and parameter usage adequately. Lacks details on post-login behavior (e.g., token lifespan) but is sufficient for the tool's complexity.

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?

Both parameters are fully described in the schema (100% coverage). The description adds context: 'If not specified, uses the default backend' for backend and 'Use this to add a new backend' for url, which extends meaning.

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?

Description clearly states 'Authenticate with a Reposit backend to enable sharing and voting', which is a specific verb+resource. It distinguishes from siblings like list_backends, search, share, vote_down, vote_up.

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?

Explicitly advises to use when authentication is required, e.g., after an 'unauthorized' error. Provides clear context but does not explicitly list when not to use alternatives.

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