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

No annotations are provided, so the description carries the full burden. It mentions trimming and formatting within length limits, which is some behavioral information, but doesn't disclose what the length limit is, what happens if the text exceeds it, whether truncation or rejection occurs, or what the output format looks like.

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 efficient sentence with no wasted words. It front-loads the core action ('Trim and format') and the output target ('meta description'). However, its brevity comes at the cost of missing important details.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't explain the length limit value, the output format, or how it handles edge cases. An agent would need to experiment to use this tool correctly.

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% and there is 1 parameter with no description. The description mentions 'a paragraph' as input but doesn't clarify the parameter's expected format, length constraints, or whether it should be plain text or HTML. With low schema coverage, the description must compensate but only minimally does so.

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 clear verb+resource: 'Trim and format a paragraph into a meta description.' This distinguishes it from SEO siblings like generate_sitemap or generate_open_graph. The only gap is that it doesn't differentiate itself from other content-formatting tools, but none of the listed siblings compete for this purpose.

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?

No when-to-use guidance, no prerequisites, and no alternatives mentioned. The description implies the tool operates on a paragraph but doesn't say when to invoke it or when not to. An agent must infer the use case from the name and description alone.

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