overview

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

With no annotations provided, the description carries full burden. It clearly labels the tool as '[READ]' (read-only), describes what it returns (fleet health statuses), and explains the parameter. However, it lacks details on authentication needs, rate limits, or whether the data is cached or real-time, which would be helpful for full transparency.

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 is concise and well-structured. The first sentence front-loads the core purpose, and the second paragraph provides usage guidance and parameter details. No wasted words; 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 the tool's simplicity (one optional parameter) and no output schema, the description provides adequate context: what it does, when to use, and parameter semantics. However, it could be improved by briefly describing the output format or any limitations, but overall it's sufficiently complete for an agent to use correctly.

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 input schema has zero description coverage for the 'target' parameter. The description compensates fully by explaining the parameter's meaning ('Endpoint-management target name from config') and usage ('omit for the default'), adding significant value beyond the 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 clearly states the tool's purpose with specific verb 'READ' and resource 'fleet health', listing included elements (online/offline, stale endpoints, version spread). It distinguishes from siblings by advising to call this first before drilling into specific tools like endpoint, login storm, or drift report.

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 explicitly states when to use ('Call this first to triage a managed-endpoint fleet') and implies when not to (before drilling into specific endpoint, login storm, or drift report). It names alternative tools that provide more detailed views.

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