IT Tools MCP Server

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

Annotations provide readOnlyHint: false, which correctly indicates this isn't a read-only operation (validation may involve processing). The description adds that it validates 'syntax and structure' - useful context about what aspects are checked. However, it doesn't disclose important behavioral details like whether it performs dry-run validation, what validation errors look like, or any rate limits. No contradiction with annotations exists.

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 phrase that directly states the tool's purpose without any wasted words. It's front-loaded with the essential information and contains no unnecessary elaboration or redundant information.

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 single-parameter validation tool with good schema coverage but no output schema, the description is minimally adequate. It specifies what's being validated (Ansible playbooks) and what aspects (syntax and structure), but doesn't explain what the validation output looks like, what happens on validation failure, or how comprehensive the validation is. The lack of output schema means the description should ideally provide more context about return values.

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?

With 100% schema description coverage (the single parameter 'playbook' is fully documented in the schema as 'Ansible playbook YAML content'), the description adds no additional parameter information. The baseline score of 3 reflects adequate coverage through the schema alone, though the description doesn't enhance understanding of parameter usage or constraints.

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: 'Validate Ansible playbook syntax and structure' - specifying both the action (validate) and the resource (Ansible playbook). It distinguishes from sibling tools like 'validate_docker_compose' by specifying Ansible playbooks, but doesn't differentiate from other Ansible-related tools like 'parse_ansible_inventory' or 'generate_ansible_inventory' in terms of when to use each.

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. While it's clear this validates Ansible playbooks, there's no mention of when to use it versus other validation tools (like 'validate_docker_compose'), when validation is needed versus other Ansible operations, or any prerequisites for using the tool effectively.

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