markdown_templates_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists templates and descriptions, implying a read-only operation, but fails to mention critical details like whether it returns all templates at once, supports pagination, or has rate limits. This leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for a simple list operation, with zero waste.

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 complexity (a list tool with one undocumented parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., format, structure), parameter usage, or behavioral constraints, making it inadequate for effective tool invocation.

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 input schema has one required parameter 'kwargs' with 0% description coverage, and the tool description provides no information about parameters. This leaves the parameter undocumented in both schema and description, failing to compensate for the low schema coverage and not adding any semantic value beyond 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?

The description clearly states the verb ('List') and resource ('available markdown templates and their descriptions'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'markdown_template_get' (which presumably retrieves a single template), leaving room for ambiguity in sibling distinction.

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 like 'markdown_template_get' or other list tools in the server. It lacks context about prerequisites, such as whether authentication or specific permissions are required, or any exclusions for usage.

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