ghl_calendar_resource_list

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds version (2021-04-15), deprecation of v3 variant, OAuth scopes (calendars/resources.readonly), and pagination details. 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?

Contains necessary details but repeats 'List Calendar Resources' and includes deprecated block syntax. Could be more concise and better structured with bullet points.

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?

Covers version, scopes, pagination, but lacks output schema or response structure details. Since no output schema exists, description should hint at return fields. Pagination usage is explained, but not how response indicates pagination state.

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 has 4 parameters with 25% description coverage. Description mentions resourceType, locationId, and pagination params (limit, skip), adding context that limit/skip are for pagination. But doesn't explain resourceType enum values beyond schema. Partial improvement over schema.

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?

Clearly states the verb 'List' and resource 'Calendar Resources', with filtering by resourceType and locationId. Distinct from sibling tools like ghl_calendar_resource_create.

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?

Provides explicit version information, deprecation warning, OAuth scopes, and pagination instructions. Lacks explicit when-not-to-use or alternatives among siblings, but the deprecation note serves as a warning against using the wrong version.

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