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

The annotations already indicate readOnlyHint=true and destructiveHint=false, which covers the safety profile. However, the description adds no behavioral context beyond the annotations—no mention of what data is returned, any rate limits, authentication needs, or edge cases. It simply restates that it gets profile information.

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 extremely short and mostly redundant: 'Get person profile' repeats the title, and the rest 'Get basic profile information for a person' adds little new meaning. The structure is not front-loaded with useful differentiating information; it is simply verbose repetition.

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?

With no output schema and an ambiguous target ('a person' – which person? the current user? a specified ID?), the description is not complete enough for an agent to know exactly what data it will receive. It is a very simple tool, but the lack of clarification about which profile is fetched and what 'basic' includes leaves gaps.

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 are zero parameters, and the schema coverage is 100% since the schema has no properties. The baseline of 4 applies because there are no parameters to describe, and the description does not need to explain parameter details.

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 verb 'get' and the resource 'person profile', and distinguishes it from sibling tools like getSharePosts by indicating it retrieves profile information, not posts. However, the phrase 'basic profile information' is somewhat vague about what fields are included.

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 explicit guidance on when to use this tool versus the siblings (createSharePost, getSharePosts). The context is implied – if you want a person's profile, use this – but there are no clear alternatives, prerequisites, or exclusions stated.

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