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

With no annotations, the description carries the full burden and covers paid nature (150 credits), auth requirement, what it does, and return fields. However, the 'truncated' field is not explained, which is a minor gap given the 'fetch ALL records' claim.

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 tight and front-loaded with the most critical info (PAID), followed by function, what it replaces, requirements, and return JSON. Every sentence adds value with no 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?

Given the tool's complexity, the description covers the core functionality, cost, auth, and output fields. It doesn't mention error conditions or truncation behavior details, but an output schema exists and the description is sufficient for an agent to decide.

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?

Schema description coverage is 0%, and the description does not explain the 'token' or 'where' parameters. Only service_url is implied via 'FeatureServer layer.' This leaves the agent guessing at parameter semantics 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 fetches all records from a FeatureServer layer, repairs geometries, and scans for problems—a specific verb+resource combo. It also distinguishes itself from siblings by explicitly naming what it replaces (query_features + fix_geometry + find_layer_issues).

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?

It explicitly states when to use this over alternatives: 'Replaces an uncapped query_features call (itself a paid-only capability) plus fix_geometry plus find_layer_issues.' It also provides essential prerequisites like Authorization Bearer token and sufficient credits balance.

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