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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description's extra details about omitted fields and required customer API access add useful context. It does not fully describe the returned operational fields, but it improves transparency beyond 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 short, front-loaded with the core action, and every sentence adds relevant information about scope, omissions, or access requirements. There is no unnecessary wording.

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 single-record getter with rich annotations and no output schema, the description provides enough context about return-field selection and access needs. It could be slightly more complete by describing the expected response shape or id source, but it is adequate.

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 description mentions using a 'known id', which identifies the parameter as a schedule identifier, but it does not explain where to get that id or add format details. With 0% schema description coverage, it only partially compensates for the schema gap.

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 and resource: 'Read one schedule using its known id.' It clearly distinguishes this as a single-schedule read tool, and the sibling tools are for different resources, so no further sibling differentiation is needed.

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?

It clearly indicates the tool requires a known schedule id and is read-only with customer API access. It does not explicitly say when not to use it or how to obtain the id, but the usage context is still clear for a single-resource getter.

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