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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context by noting the tool returns the same public creations as the website, returns descriptive data and links, and is meant for recommending real creations. No contradiction with annotations.

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?

Two sentences carry the action, scope, output, and usage scenario with no filler. The key information is front-loaded, and every clause adds value.

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?

With no output schema, the description still tells the agent what kind of data to expect ('descriptive data and links'). Combined with fully documented parameters and safety annotations, this is enough for confident selection and invocation, though it stops short of detailing exact return fields.

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?

Schema description coverage is 100%, so the parameters are already fully documented in the input schema. The description does not add parameter-specific semantics beyond that, which meets the baseline 3 for high schema coverage.

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 opens with a specific verb and resource: 'Search or browse the public Mana community' and clarifies the scope with 'the same creations the website shows.' It also states the output ('Returns descriptive data and links'), making it easy to distinguish from siblings like get_mana_creation or list_mana_tags.

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?

It gives a clear intended use case: 'Use this to recommend real Mana creations to a person, and link the returned url so they reach the creator.' This tells an agent when to invoke the tool, but it does not explicitly contrast it with get_mana_creation or other siblings, so it lacks when-not guidance.

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