get_summary_wildlife_lands

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

With no annotations, the description must carry the behavioral burden. It indicates a read-style operation by saying 'Return', but it does not disclose the scope, format, or any side-effect or authorization details. This is acceptable for a zero-parameter read-only tool, but still minimal.

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 a single, front-loaded sentence with no filler. For a tool with no parameters, this is maximally concise while still stating the primary action and resource.

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?

The tool is trivially invocable with no arguments, but the absence of an output schema and lack of detail about what the 'summary' contains leaves some ambiguity. It is adequate for simple selection, but an agent must infer the exact return structure.

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 parameters, so the description has no parameter details to provide. The baseline for 0 params is 4, and the description appropriately says nothing about parameters.

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 uses a clear verb and resource: 'Return a summary of wildlife lands.' It is distinguishable from sibling transmission-line tools by the resource term, but 'wildlife lands' and the exact nature of the summary are left undefined, preventing a top score.

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?

No explicit guidance on when to use this tool rather than a sibling is provided. The resource 'wildlife lands' implies it is for wildlife-lands summaries, but there are no stated alternatives, contexts, or exclusions, so usage is only implied.

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