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

The description adds context beyond the annotations by disclosing that the operation is 'Not metered' and requires a free Prowlo account. It also hints at how to obtain an account via 'call it to get a signup link'. This supplements the destructiveHint and idempotentHint annotations with useful operational details, although the phrase 'call it' is somewhat ambiguous.

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 short and front-loaded with the main action. The second sentence adds relevant notes on metering and account requirements, though the phrase 'call it' is slightly awkward and could be misinterpreted. Overall, it is appropriately sized with no redundancies.

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 delete tool with one parameter and no output schema, the description covers the essential purpose, a parameter reference, and unique operational conditions (metering, account requirements). While it does not detail return values or error behavior, the annotations (destructiveHint, idempotentHint) fill the safety profile, making the description reasonably complete.

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 schema already fully documents the sole parameter 'id' with description 'Trend id to delete (from trend_list)'. The description repeats 'by id' without adding new semantics. Since schema coverage is 100%, the baseline score of 3 applies; the description does not enhance parameter understanding.

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 clearly states the action ('Delete a Trend by id') with a specific verb and resource. It distinguishes from sibling tools like trend_get, trend_list, trend_update, and trend_create by explicitly indicating deletion. The resource name 'Trend' is unambiguous.

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 description provides some usage context: 'Not metered' and 'requires a free Prowlo account — call it to get a signup link'. This implies that usage is conditional on account creation and that the operation is not metered. However, it does not explicitly state when to use this tool versus alternatives (e.g., trend_update for modification) or provide exclusions.

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