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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'List' and 'GET /v1/profiles'. It adds the endpoint detail and confirms this is a read-only operation, but provides no further behavioral context such as pagination, output shape, or authorization requirements. Given the existing annotation, this is adequate but not rich.

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?

Two short sentences, one describing the operation and one giving the exact API endpoint. Every word adds value, and the core purpose is front-loaded in the first sentence.

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 list operation, the description is complete enough to call the tool correctly. It does not describe the return payload, but the absence of an output schema and the low complexity make this a minor gap rather than a significant omission.

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 tool has zero parameters, so no parameter documentation is needed. The description adds no parameter-related meaning, but the baseline of 4 applies because there is nothing for the schema or description to explain.

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?

States a specific verb ('List') and resource ('connected calendar accounts/profiles linked to this Cronofy account') with concrete examples. It also names the API endpoint, and clearly distinguishes this from sibling cronofy_list_calendars by focusing on accounts/profiles rather than calendars.

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 gives clear context: use this when you need the connected calendar accounts/profiles for the Cronofy account. It does not explicitly mention when not to use it or name alternatives, but the resource distinction from sibling tools is clear enough for basic selection.

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