cursor_agent_analyze_files

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

No annotations provided, and the description (5 words) reveals almost no behavioral traits. Does not mention side effects, permissions, idempotency, or any constraints beyond basic function.

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?

Very concise (5 words), but this brevity sacrifices needed information. Adequate for a simple tool, but for 13 parameters, it's under-specified.

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 13 parameters, no output schema, and no annotations, the description is woefully incomplete. No explanation of return values, behavior, or setup requirements.

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 schema coverage at 46% (low), the description should compensate but only mentions 'paths' and 'optional prompt' without adding details. No parameter documentation beyond 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 states 'Analyze one or more paths', which gives a verb and resource, but 'analyze' is vague and doesn't distinguish from sibling tools like search_repo or plan_task. No differentiation provided.

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 on when to use this tool versus alternatives. Missing context for appropriate scenarios or exclusions.

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