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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by saying results are deterministic and include provenance, which is not present in the annotations and helps set expectations about repeatability and traceability.

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?

It is a single front-loaded sentence with no filler. The returned categories are listed compactly, and 'with provenance' is a useful qualifier rather than padding.

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?

Because an output schema exists and annotations are rich, the description need not explain return values or safety. Still, given the unusually crowded sibling set of profile, contact, fact-pack, and capability tools, the description should do more to clarify what this aggregate tool includes that the narrower tools do not.

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 tool takes zero parameters, so there are no parameter semantics to explain. The baseline for a no-parameter tool is 4, and there is no schema complexity the description needs to compensate for.

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 names several content categories (profile, contact, process, personality, capability-limit signals) and says it returns them with provenance, so the general purpose is inferable. However, 'signals' is vague, the professional-profile framing comes mostly from the title, and it does not distinguish this tool from overlapping siblings such as get_profile_fact_pack, get_contact_email, or get_agent_capabilities.

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?

There is no statement of when to use this tool, when not to use it, or which sibling to prefer for narrower needs. An agent must guess between this aggregate profile tool and the many more specific profile/contact/capability tools.

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