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

The annotations already convey that the operation is read-only, idempotent, non-destructive, and broadly accessible. The description adds no additional behavioral context such as possible error conditions or data scope, but it does not contradict 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 repeats the same statement twice: 'Returns the details of a given prospect of your shop app.' followed by 'Guidance: Returns the details of a given prospect of your shop app.' It also includes a confusing trailing fragment '| context: user_id,' making it less concise than it should be.

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 operation, the description is adequate, but it is vague about what 'details' are returned and there is no output schema to clarify the response structure. It does not fully cover expected return content or error behavior.

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 only parameter, user_id, is already documented in the schema as 'Unique ID of the User.' The description does not add further meaning beyond referring to a 'given prospect,' so it provides no extra value beyond the existing schema coverage.

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 clearly states the tool returns details of a specific prospect, using a specific verb and resource. It is distinct from sibling tools like shop_list_prospects and shop_get_customer because it targets a single prospect.

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 provides no guidance on when to use this tool versus alternatives such as shop_list_prospects or other shop_get_* tools. It does not mention prerequisites, conditions, or exclusions.

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