cryptbrew_lock_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists product features but does not state that the tool is a read-only information source, describe the return format, or mention any side effects, permissions, or network behavior.

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 sentence that front-loads the product name and packs the key distinguishing details (separate Mac app, features, price, exclusion of invoicing). It is efficient, though the colon-separated list is dense and the tool action remains implicit.

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 a parameterless info tool with no output schema, the description provides useful product content and disambiguation. However, it does not state what the tool returns or how it relates to the many sibling info tools, leaving meaningful gaps for an agent deciding whether to call it.

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 tool takes zero parameters, so there is no parameter semantics to document. By the baseline rule for 0 params, a score of 4 is appropriate because the description does not need to compensate for missing parameter details.

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 names the subject (CryptBrew Lock) and lists specific product attributes, but it never states what the tool actually does, such as returning information about CryptBrew Lock. It disambiguates from the 'invoicing 1% fee' product but does not differentiate from sibling tools like cryptbrew_about or cryptbrew_pricing.

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 phrase 'CryptBrew Lock only' and 'Not the invoicing 1% fee' imply a scope constraint, but there is no explicit guidance on when to use this tool versus the sibling tools (e.g., cryptbrew_pricing, cryptbrew_faq, cryptbrew_about). The agent is left to infer usage.

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