validate_repository

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds meaningful context beyond that: it operates offline, does not execute project tools, requires no Apple credentials, and omitted fields remain unmanaged. This gives the agent important behavioral information that structured annotations alone do not convey.

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 two sentences with no filler. The primary action and scope are front-loaded, followed by compact behavioral constraints. Every sentence earns its place.

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?

The description is strong on safety and environmental context (offline, non-mutating, no credentials) but weaker on operational completeness. With no output schema and zero schema description coverage, it should also clarify what validation results look like and how the five parameters relate to the validation scope. The missing parameter detail and output expectations keep this from being fully complete.

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%, so the description carries the burden of explaining parameters. It references 'domains/locales' generically but does not explain the required 'root' parameter, nor 'version' or 'platform', and gives no guidance on how omitted fields relate to the schema. The phrase 'Omitted fields remain unmanaged' hints at behavior but does not clarify parameter semantics.

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 a specific verb ('Validate') and identifies the resource scope ('selected AppStore domains/locales') plus the offline nature of the operation. It is clear enough to differentiate from a general validation tool, though it does not fully explain what 'validate' means in terms of checks or output.

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 clear context for when to use this tool: offline validation without Apple credentials, and it explicitly states what the tool does not do (mutate files, execute project tools). It stops short of naming an alternative tool or giving an explicit when-not-to-use statement, so it loses one point.

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