Get All Company Groups

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

The description adds pagination behavior (use page/per_page, response includes pagination metadata) beyond the readOnlyHint annotation. However, it incorrectly references 'Resource Planning records' instead of groups, partially undermining transparency.

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 relatively short but includes a misleading and unnecessary sentence about specific record fetching, which wastes space and could be removed or corrected.

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 description lacks details about the returned group objects (e.g., fields included) and inaccurately describes the response as 'Resource Planning records' instead of groups. This is insufficient given the absence of an output schema.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining pagination control and metadata response, which is not explicit in the schema descriptions.

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 first sentence correctly states 'Gets all Groups in a given Company,' but the second sentence contradicts this by saying 'fetch the full details of a specific Resource Planning records by its identifier,' which is inaccurate for a list-all tool. This muddles the purpose.

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 provides no guidance on when to use this tool vs. alternatives like 'get_a_single_group'. The misleading statement about fetching a specific record further confuses appropriate usage.

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