get_problem

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

No annotations are provided, so the description bears full responsibility. It correctly indicates a read-only retrieval operation and discloses the content scope. However, it does not mention any implications like authentication requirements, rate limits, or data freshness. A 3 is reasonable as it is adequate but not exhaustive.

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?

Two sentences: first immediately states the primary purpose, second provides essential post-fetch guidance. Every word carries weight, no redundancy or filler.

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?

For a simple retrieval tool with one parameter and no output schema, the description covers all needed context: what it does, what it returns (list of details), and the next action. No gaps remain.

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?

The single parameter titleSlug already has a precise description in the input schema (100% coverage). The tool description adds no further semantic value beyond restating the tool's purpose. Baseline 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 tool retrieves details about a specific LeetCode problem, listing the types of information included (description, examples, constraints, related info). This distinguishes it from siblings like get_daily_challenge (specific challenge) or get_problem_solution (solutions).

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 explicit guidance on what to do after fetching (invoke learning_mode and problem_workflow prompts). While it doesn't specify when not to use or mention alternatives like search_problems, the context is clear for an agent to use appropriately.

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