getCriticalPoints

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It clearly states that the tool returns critical operations and gives concrete examples, indicating a read-only analysis. While it could mention whether the tool is expensive or has auth requirements, the description is sufficiently transparent for a static analysis tool.

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 consists of two succinct sentences. The first sentence clearly states the purpose, and the second adds distinctive value. Every sentence earns its place without redundancy or fluff.

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 tool has one optional parameter and no output schema, the description explains the core functionality and parameter optionality well. It lacks explicit mention of the return structure (e.g., list of operations with details), but for a simple tool, it is nearly 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 100%, so the baseline is 3. The tool description adds context about 'critical operations' and the unique value, but does not provide additional semantics for the entryPoint parameter beyond what the schema already says. Thus, a score of 3 is appropriate.

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 the verb 'Get all critical operations' and specifies the resource: critical operations reachable from a function. It lists examples (database reads/writes, HTTP requests, file I/O, exec calls) and explicitly highlights the unique value compared to raw search, distinguishing it from sibling tools like searchSymbols.

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 implies when to use this tool by stating 'This is the unique value of MCP vs raw search,' suggesting it's for semantic classification rather than simple search. However, it does not explicitly exclude alternative siblings or provide clear 'when not to use' guidance, so it achieves a 4.

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