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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'canonical' and 'public' context, which hints at authoritative and publicly scoped facts, but it does not disclose additional behavioral traits such as response shape, rate limits, or authentication requirements.

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 sentence delivers the essential action and resource without repetition or filler. The key term 'canonical SHAR identity' is front-loaded, and no sentence is wasted.

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 zero-parameter, read-only retrieval tool with strong annotations, this description is mostly complete: it names what is returned and implies a non-destructive, stable lookup. It does not explain what SHAR identity means or enumerate the organization facts, but the simplicity of the tool limits the severity of that 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?

The tool has zero parameters and the schema fully documents that with an empty properties object. Per the rubric, a zero-parameter tool receives a baseline of 4, and no parameter-level description is needed.

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?

Description states a specific verb ('Retrieve') and a specific resource ('canonical SHAR identity and public organization facts'), making the tool's core purpose clear. It reads distinctly from siblings like get_public_clients and get_industry_experience, though it does not explicitly contrast itself with 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?

No guidance is provided about when to use this tool versus alternative get_* tools in the sibling list. There are no exclusions, conditions, or mentions of alternatives, leaving the agent to infer usage purely from the name and one-line description.

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