management_profile

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds valuable behavioral disclosure: the data is pattern-extracted from narrative search snippets, so identity must be verified against the source URL before quoting. This goes beyond the annotation safety profile by flagging potential unreliability. 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?

The core action is front-loaded in the first sentence, and the second sentence contains the important caveat. The text is compact at roughly two sentences, though the second sentence is slightly convoluted with the 'Every real initiating-coverage note' construction.

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?

The description names the output fields and the reliability caveat, which is helpful given there is no output schema. However, it does not explain how optional context fields like sector, listed, or country affect the lookup, nor the return shape beyond field names, so an agent may have to infer some invocation details.

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?

With schema description coverage at 0%, the description needed to explain the required context.company and the optional filters, but it does not. 'Company's own site' loosely hints at companyDomain, and 'company' is inferable from the subject matter, but no explicit parameter guidance is provided.

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 a specific action ('Retrieves') and resource ('key management personnel and board member profiles') and enumerates the data fields (name, designation, background) and sources. It does not explicitly position the tool against siblings such as management_commentary or promoter_background, so it falls short of full sibling differentiation.

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 gives a purpose but no when-to-use guidance, prerequisites, or comparisons to alternative tools. The second sentence explains data provenance and a verification requirement, but it does not tell an agent when to choose this tool over management_commentary, promoter_background, or company_profile.

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