cryptbrew_links

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

With no annotations, the description carries the full burden, and it does disclose the exact contents returned (website, help, support, downloads, llms.txt, API, App Store, health). For a zero-side-effect static link resource there is little further behavior to reveal, though it does not state the return shape (structured list vs. markdown).

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?

A single dense sentence that front-loads the resource type and then lists every entry; nothing is wasted. The lead-in phrase 'Official Cryptbrew invoicing URLs' is slightly garbled, since the listed links are not invoicing-specific.

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?

No output schema and no parameters exist, so the description is largely complete for such a simple static-links tool, enumerating the payload contents. It misses the response format and does not resolve the overlap with cryptbrew_health/cryptbrew_contact.

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 the baseline of 4 applies; there is nothing for the description to clarify beyond what the schema already shows.

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 a specific resource set (official Cryptbrew URLs) and enumerates the concrete links returned, so an agent knows exactly what it gets. It offers no differentiation from siblings, and the 'health' link overlaps confusingly with the sibling tool cryptbrew_health.

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?

There is no when-to-use statement, no condition that selects this tool over cryptbrew_health or cryptbrew_contact, and no mention of when a raw link list is preferable to those dedicated tools. Usage is only implied by the content list.

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