check_project_compliance

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

No annotations are provided, so the description carries full burden. It implies a read-only analysis ('check'), but doesn't disclose behavioral traits such as what 'compliance' means, whether it's a quick scan or deep audit, if it requires specific permissions, or what the output format might be. This leaves significant gaps for a tool with no structured safety hints.

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 in Russian that directly states the tool's purpose. It's front-loaded with no wasted words, making it appropriately concise for its limited content.

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 of a compliance check tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on what 'basic compliance' entails, how results are returned, or interaction with sibling tools, making it inadequate for informed agent use.

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 must compensate. It mentions 'UI/локализации' (UI/localization) but doesn't explain the 'project_path' parameter—what it expects (e.g., file path, directory, project ID) or how it relates to the compliance check. The description adds minimal meaning beyond the bare 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 'Проверить базовое соответствие UI/локализации' (Check basic UI/localization compliance) states a clear verb ('check') and target ('UI/localization compliance'), but it's vague about what 'basic compliance' entails and doesn't distinguish from siblings like 'validate_ui_usage' or 'analyze_project'. It provides a general purpose without specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'validate_ui_usage' and 'analyze_project', the description lacks context on prerequisites, exclusions, or comparative use cases, leaving the agent to guess based on tool names alone.

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