Buscar mensajes

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context beyond that: the mandatory-criterion constraint and the return ordering ("Devuelve los UID más altos, que en cPanel suelen ser los más nuevos"), which tells the agent how results are sorted. Not exhaustive, but a real addition over the 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?

Four short sentences, front-loaded with the core action and the hard constraint, with zero padding. Slight redundancy with the schema's date descriptions, but otherwise tight.

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 10-parameter tool with 50% schema coverage and no output schema, the description covers the criterion requirement and result ordering, which is helpful since there is no output schema. But it omits guidance for the undocumented parameters and any routing versus list_messages, leaving meaningful gaps.

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 coverage is only 50% across 10 parameters, so the description must compensate more than it does. Its date info ("since y before usan YYYY-MM-DD") largely duplicates the schema descriptions, and it adds nothing for mailbox, limit, text, flagged, or subject. Marginal value over the schema.

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?

"Busca dentro de una carpeta" states a clear verb+resource and adds the requirement of at least one criterion. However, it never distinguishes itself from the sibling list_messages, so an agent cannot tell from the text alone why it would pick search over list. Clear purpose, absent sibling differentiation.

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?

"Exige al menos un criterio" implies usage (call this when you have a filter criterion), but the description gives no explicit when-to-use/when-not guidance and never names an alternative such as list_messages or unseen_summary. Usage is only inferred from the constraint.

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