discover_services

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

Discloses that this is a fast discovery only, returns no graph data, and describes the edge case when no config file exists. No annotations are provided, so the description carries full burden and meets it.

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?

Well-structured with bullet points, workflow steps, and a tip. Front-loaded with purpose. Slightly lengthy but efficient, every sentence adds value.

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 zero parameters and no output schema, the description fully covers purpose, usage, return values, workflow, and edge case. 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?

No parameters, so schema coverage is 100%. The description adds value by explaining the return values (service names, paths, entry points) and workflow, exceeding the baseline of 4 for zero-param tools.

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 discovers services in a project without full analysis, distinguishing it from analyze_project. It uses specific verbs and resources and includes the phrase 'before running analyze_project' to differentiate siblings.

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 states when to use (during onboarding), when not (before full analysis), and provides a workflow step-by-step. It also mentions an alternative (write_config) for saving configuration.

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