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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful behavioral context beyond that: the exact API endpoint, the ability to select fields including nested sub-resources, and the fact that it returns the profile object.

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?

Three short sentences, each earning its place: the core purpose, the API endpoint, and the parameter behavior. The most important information is front-loaded, and there is no redundancy.

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 read-by-id tool with one required parameter and full schema coverage, the description covers purpose, endpoint, parameter use, and return value. There is no output schema, but 'Returns the profile object' adequately addresses the return expectation.

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 coverage is 100%, so the baseline is 3. The description adds value by naming concrete nested sub-resources (appointmentTypes, teamMembers, locations) that the schema does not list, giving the agent a clearer picture of what the fields parameter can express.

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 explicitly states 'Fetch a single profile (booking page) by id,' giving a specific verb, resource, and scope. This clearly distinguishes it from list_profiles and other sibling tools that operate on collections or different resources.

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 fetching one profile by id. It does not explicitly name list_profiles as the alternative for fetching multiple profiles, but the single-by-id framing makes the usage boundary obvious.

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