list_surveyors

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

No annotations are provided, so the description carries the full disclosure burden and it does deliver the essentials: the return content (names plus what each discovers) and a hard prerequisite relative to survey. It stops short of stating that the call is side-effect free or cheap to repeat, which for a zero-parameter list is a minor residual gap rather than a risk.

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 short sentences, zero filler, with the enumeration purpose front-loaded and the sequencing advice second. Every clause carries distinct information.

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 no-argument, read-style enumeration tool with an output schema covering the return shape, the description supplies the only things the structured fields cannot: what is listed and when to call it relative to survey. Nothing an agent needs in order to invoke it correctly is missing.

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?

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly adds no pseudo-parameter detail, though it also doesn't note that the scope is implicitly "this build" as opposed to all builds.

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?

States a specific verb ("Name") and resource ("the surveyors this build has") plus the payload ("what each discovers"). This is immediately distinguishable from the survey sibling, which performs the survey rather than enumerating available surveyors.

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 prescribes ordering ("Call it before survey") and gives the reason ("so the surveyor you ask for is one that exists"). It names the alternative tool and the condition that should route the agent here first, leaving nothing to inference.

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