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

Annotations already disclose read-only, idempotent, non-destructive behavior, so the description does not need to repeat those. It adds the returned field categories, but does not discuss authentication, company scoping effects, or error/return behavior. No contradiction with 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?

A single front-loaded sentence states the operation and the data categories with no filler or repetition. It is immediately scannable and every phrase adds useful information.

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-only getter, with annotations covering safety and a schema covering the only optional parameter, the description gives enough high-level information. Without an output schema it enumerates the returned categories, though it does not clarify whether companyId changes the result or when it should be supplied, which is 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?

Schema description coverage is 100%, so the optional companyId parameter is already documented. The description adds no extra meaning about when companyId matters or how it affects the returned profile. The baseline 3 applies because the schema carries the parameter semantics.

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 action ('Get') and resource ('current user's profile information') and enumerates the content covered (name, title, contact info, personal details). It is clear and distinguishable from similar tools like get_my_role or get_reader_profile, though it does not explicitly name any sibling.

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 implies use when the current user's profile data is needed, but provides no explicit when-not guidance or comparison to alternatives such as get_my_role, get_reader_profile, or update_my_profile. No exclusions or conditions are mentioned.

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