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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds that it targets the authenticated account and lists the fields returned, which is useful but does not go beyond that. It does not mention authentication requirements, rate limits, or response format, though the annotations lower the burden.

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 a single focused sentence that names the operation, the target, the key returned fields, and the API endpoint. There is no filler or redundancy, and the most important information appears immediately.

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 zero-parameter, read-only account metadata lookup, the description is nearly complete: it identifies the resource, the fields returned, and the REST endpoint. It lacks output schema details and error/edge-case information, but the simplicity of the tool and the readOnlyHint annotation make this a minor gap.

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 the baseline is 4. The description correctly implies no inputs are needed and focuses on the output fields. There is no parameter detail required beyond what the empty schema already communicates.

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 states a specific verb ('Get'), resource ('authenticated Cronofy account's details'), and enumerates the returned fields (id, email, name, default tzid, locale). It is clear and distinct from siblings in practice, though it does not explicitly contrast itself with cronofy_get_userinfo, which could be confused without deeper inspection.

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 no guidance on when to use this tool versus the siblings such as cronofy_get_userinfo, cronofy_list_profiles, or cronofy_list_calendars. It only states what the tool does and the API endpoint, leaving the agent to infer usage from the tool name.

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