Get Groups For Layer

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

Annotations already declare readOnlyHint=true, so the description correctly implies a safe read operation. It adds value by stating the return type (paginated JSON array) and including pagination metadata. No contradictions.

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 reasonably concise but includes unnecessary repetition (e.g., 'Document Markup records' twice) and a confusing sentence about fetching a specific record. It is front-loaded with the main action but could be more streamlined.

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?

No output schema exists, so the description partially compensates by describing the return value and pagination. However, it lacks details about the structure of a Document Markup record. Given the tool's complexity, it is minimally adequate.

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 coverage is 100% with good descriptions. The description restates required parameters and pagination control, adding minor context beyond the schema. Baseline 3 is appropriate as it does not significantly enhance the schema's information.

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 states the core purpose as retrieving all groups within a layer, but includes contradictory phrasing about fetching a specific Document Markup record. This ambiguity reduces clarity. The tool name and title are clear, but the text is confusing.

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 does not explicitly state when to use this tool versus alternatives like get_groups or get_layers. It mentions pagination control but lacks guidance on context or exclusions. No sibling differentiation is provided.

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