markdown-to-notion

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the conversion function without mentioning any behavioral traits: no information about error handling, performance characteristics, rate limits, authentication needs, or what happens to invalid markdown. This leaves the agent with significant uncertainty about how the tool behaves in practice.

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 concise - a single sentence that directly states the tool's function with zero wasted words. It's perfectly front-loaded with the essential information. This is an excellent example of efficiency in description writing.

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?

Given the tool's purpose (format conversion), absence of annotations, no output schema, and 0% schema coverage, the description is insufficiently complete. It doesn't address what the output looks like (beyond 'notion json page content'), error conditions, or practical usage considerations. For a conversion tool with no structured documentation support, more context is needed.

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% (no parameter descriptions in schema), and the tool has 1 parameter. The description mentions 'markdown content' but provides no additional semantic context about the parameter: no format requirements, size limits, supported markdown features, or examples. It doesn't compensate for the complete lack of schema documentation.

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 tool's purpose: 'Convert markdown content to notion json page content' - a specific verb ('convert') and resources ('markdown content' to 'notion json page content'). It's unambiguous about what transformation it performs. However, with no sibling tools mentioned, there's no explicit differentiation from alternatives, preventing a perfect score.

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 versus alternatives. It doesn't mention prerequisites, constraints, or typical use cases. While the purpose is clear, there's complete absence of contextual usage instructions.

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