analyze_project

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

Annotations already mark readOnlyHint=true, so no contradiction. Description adds specific detection details (Tailwind v3/v4, SVG loader) and server filesystem behavior, enhancing transparency without redundancy.

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?

Description is informative and well-structured, starting with purpose, then usage, then specifics. Though lengthy, every sentence adds value for a complex detection tool.

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?

Covers detection details and relationship to siblings. Lacks explicit output format specification, but mentions 'reports tailwindVersion' and SVG mode/hint, which is satisfactory given no output schema.

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 coverage is 100% and describes rootDir well. Description adds default behavior ('defaults to server cwd'), which adds meaning beyond schema, justifying above baseline.

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 it detects project profile (framework, language, styling, etc.) and distinguishes from siblings by noting those tools run detection internally, so this is for isolated inspection.

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?

Explicitly says 'call this only to inspect detection in isolation (no Figma, no file scan)', providing clear when-to and when-not-to guidance.

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