Get Accessible Groups For Authenticated User By Context

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the overall read-only behavior is clear. The description adds the endpoint and return type information, but the confusing statement about Document Markup records detracts from clarity. No contradiction with annotations.

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 brief but contains a contradictory sentence that undermines clarity. It is not optimally concise due to redundant or misleading information.

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?

There is no output schema, and the description's claim that it returns 'a JSON object describing the requested Document Markup records' is vague and inconsistent with the stated purpose of retrieving groups. Additionally, no pagination details are provided despite page/per_page parameters being present.

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?

Input schema has 100% description coverage, so parameters are well-documented there. The description lists required parameters but does not add additional meaning beyond the schema. Baseline score of 3 is appropriate.

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 initially states 'Retrieve all groups accessible to the authenticated user for a given context type and ID' but then contradicts by saying 'Use this to fetch the full details of a specific Document Markup records by its identifier.' This suggests a copy-paste error, making the purpose confusing and inconsistent.

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 provide any guidance on when to use this tool versus alternatives. No explicit context or when-not-to-use instructions are given, leaving the agent without decision support.

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