marketsharp_appointments_get

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the field set an agent can expect, but says nothing about behavior for a missing or invalid ID (error vs empty) and nothing about authorization scoping.

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?

One short sentence with the retrieval action front-loaded and no wasted wording. The returned-field list is dense but earns its place by telling the agent what comes back in the absence of an output schema.

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 read with one fully documented parameter and complete read-only annotations, the definition is nearly sufficient. The only real gap is the absence of any note about what happens when the ID is not found.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that appointmentId is a MarketSharp appointment ID. The description's "by ID" phrasing adds no format or sourcing detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ("Get one appointment by ID") and enumerates the returned fields (time, salespeople, type, result, address). This distinguishes it from the sibling list/search tools by making clear it is a single-record fetch, though it never names a sibling explicitly.

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 "by ID" phrasing implies the tool is for retrieving one known appointment, with marketsharp_appointments_list being the natural alternative for enumeration. However, no explicit when-to-use or when-not-to-use guidance is given, so the routing must be inferred.

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