Get URI

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

Annotations already indicate readOnlyHint=true, so the description adds value by clarifying that URI values are 'non-secret scalar results.' However, it does not discuss error handling (e.g., behavior when no match is found) or authentication needs, which are partially covered by the read-only annotation.

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 concise with two sentences, each serving a purpose: the first states the function, the second provides usage guidance and output clarification. No unnecessary words, and the key points are front-loaded.

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 (one parameter, output schema exists, annotations present), the description fully covers the necessary context. It explains the tool's purpose, term usage, and output nature, leaving no significant gaps for an AI agent to misinterpret.

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 already provides a detailed description of the 'term' parameter (100% coverage), making the description's mention of 'bw get uri' context light. The description adds no new parameter semantics beyond the schema, so a baseline score of 3 is appropriate.

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 'Get the first login URI matched by bw get uri for a search term,' specifying the verb, resource, and context. It distinguishes from sibling tools like 'keychain_get_password' and 'keychain_get_item' by focusing on the URI retrieval, and mentions the output is 'non-secret scalar results.'

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 advises using an exact item id to avoid ambiguity, which guides the agent on when to provide precise input. However, it does not explicitly state when to use this tool over alternatives like keychain_get_item, but the context of retrieving only the URI implies its specific use case.

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