validate_structure

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 behavioral traits. The verb 'validate' implies a read-only operation, but the description does not confirm whether it has side effects, what happens if the project doesn't exist, what the output format is, or any permission requirements. This leaves the agent with insufficient behavioral context.

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 sentence with no filler or redundancy. It is front-loaded with the core action and resource, making it immediately scannable. Every word serves a purpose.

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 output schema and no annotations, the description must provide enough context for the agent to understand expected behavior. It lacks an explanation of what 'infrastructure pieces' includes, what a successful validation returns, and how this differs from similar sibling tools. The absence of this information makes the tool feel incomplete in context.

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 schema has 0% description coverage for the single required parameter 'project_path'. The description mentions 'in a project' but does not explicitly connect this to the parameter or clarify what value should be passed. There is no guidance on path format, whether it should be absolute or relative, or how it is used.

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 uses the specific verb 'validate' and identifies the resource as 'infrastructure pieces' within a project, providing a clear subject and scope. It distinguishes itself from siblings like 'list_patterns' or 'agentic_health' by focusing on validation of structural existence rather than listing or health status. However, 'qué piezas' is slightly ambiguous, as it could imply either validation against an expected set or simple enumeration.

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?

There is no explicit or implicit guidance on when to use this tool versus its many siblings. The description simply states what the tool does without mentioning circumstances, preconditions, or alternative tools. For a tool in a large family like this, this is a significant gap.

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