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

With no annotations provided, the description carries the full burden of disclosing behavior, but it reveals nothing about whether the tool reads, writes, transforms, or returns content. It also fails to mention any side effects, permissions, or output expectations.

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 extremely short, but this is under-specification, not conciseness. The single label 'V1 Markdown' adds no meaningful information and fails to earn its place as the description.

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 three parameters, no annotations, and no output schema, the description is wholly inadequate. It omits purpose, usage, parameter semantics, and any behavioral details, leaving almost all context to be guessed.

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 the description does not compensate. The three parameters (url, maxTimeout, include_links) remain unexplained—an agent cannot infer their types, constraints, or how they affect tool behavior from the phrase 'V1 Markdown'.

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 'V1 Markdown' is a version label, not a statement of purpose. It does not mention any verb or resource, and it fails to distinguish the tool from siblings 'extract' and 'news_article', leaving the agent to guess what the tool actually does.

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 no guidance on when to use this tool, nor does it reference alternatives or conditions for choosing between 'markdown', 'extract', or 'news_article'. An agent has no basis to select this tool over its siblings.

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