people_get_all_modules

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds useful context beyond annotations, such as prerequisites (read permissions) and error recovery (verify People product access and API permissions), without contradicting the 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 well-structured with labeled sections: main purpose, prerequisites, next steps, workflow, and error recovery. Every sentence adds value, and the main purpose is front-loaded in the first line.

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?

For a simple zero-parameter discovery tool, the description covers purpose, prerequisites, next steps, workflow, and error recovery. This is sufficient for an agent to know when and how to invoke the tool, even without 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?

The input schema has zero parameters, so baseline 4 applies. The description does not need to explain parameters, and it correctly avoids inventing any.

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 'Get all available Zoho People modules' with examples (Employees, Departments, Attendance, etc.), using a specific verb and resource. It distinguishes itself from the sibling tool crm_get_all_modules by specifying 'Zoho People' and from other People tools by its scope.

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 clear usage context through 'Prerequisites' (Zoho People access with read permissions), a 'Next Steps' chain (people_get_fields → people_search_records), and a 'Workflow' (module discovery → field analysis → record operations). However, it does not explicitly state when not to use this tool or name alternative modules-listing tools, so it lacks explicit exclusions.

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