ram_search_characters

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds no behavioral detail beyond that, such as pagination behavior, matching semantics, result limits, or how multiple filters combine.

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 definition is a single front-loaded sentence with no filler. Every word contributes to identifying the resource and its supported filters.

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 simple read-only search tool with annotations and no output schema, the description gives enough to attempt a basic call. However, it leaves pagination and matching behavior undocumented, which matters for a five-parameter search endpoint with no schema descriptions.

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 0%, so the description must compensate, but it only mentions four of the five parameters. It omits the page parameter entirely and does not clarify name matching behavior or how filters interact. Enum values are visible in the schema, but the description adds little semantic meaning beyond repeating property names.

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 states a specific verb and resource: 'Search Rick and Morty characters,' and lists the main filterable dimensions. It is clear enough to distinguish a search endpoint from a generic getter, though it does not explicitly name ram_get_character as the alternative.

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?

Listing name, status, species, and gender implies the tool is for filtered character lookup, but there is no explicit guidance on when to use this versus ram_get_character or when not to use it. The usage context is inferable rather than stated.

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