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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing further: it doesn't say what 'inspect' yields, whether results are truncated, or how large collections behave, all of which matter given the limit parameter exists to prevent huge responses.

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?

A single front-loaded sentence with no filler, which is efficient. That brevity, however, tips into under-specification rather than economy — there is no second sentence carrying the guidance the tool needs.

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?

With a nested input object, two required parameters, 0% schema description coverage and no output schema, the definition should explain the input shape and roughly what is returned. Instead it leaves the agent to reverse-engineer the nested payload and result format from the schema alone.

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 reported as 0% and the description mentions neither projectId nor the nested input object, so nothing clarifies how collectionId and limit are supplied. The pagination cap (default 50, max 100) is a key semantic the description could reinforce but does not.

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 pair ('list and inspect') and a concrete resource ('geospatial datasets in a collection attached to the project'), so the agent knows the operation is a scoped read of collection contents. It does not name or distinguish itself from near siblings like project_inspect_source or search_view, which is what a 5 would require.

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?

There is no when-to-use guidance and no mention of alternatives, despite many sibling tools that also read project/source data (project_inspect_source, search_view, resource_view). The agent must infer selection criteria from names alone.

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