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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral detail: 'Preferences that are not stated there are reported as not stated', which informs the agent about how unverified information is handled. However, it does not describe output format, edge cases, or how the 'public record' is scoped, so it adds only modest value beyond the 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 description is extremely concise—two sentences that state the purpose and a key nuance. It front-loads the core function without any redundant words or filler. Every sentence earns its place, making it an exemplary concise definition.

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 tool with one optional parameter, no output schema, and annotations covering safety, the description is reasonably complete. It clarifies what is returned and how unstated preferences are reported. However, it could better explain the role of the 'question' parameter in shaping results and explicitly differentiate from the sibling 'experience-and-skills' tool, which is a minor gap. Overall, it is sufficient for an agent to call it correctly.

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 schema fully describes the single parameter ('question') with a description, so the schema itself provides the semantics. The tool description does not elaborate on how the question parameter affects the results, so it adds no additional meaning beyond what the schema already states. This warrants the baseline score of 3 for high schema coverage.

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 verb ('returns') and resource ('work and collaborations described in the public record'), which is clear. It also adds a nuance about unstated preferences. However, it does not explicitly distinguish itself from the sibling tool 'experience-and-skills', which could overlap in scope, so it is not a 5.

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 given on when to use this tool versus its siblings. The description does not mention alternatives, conditions for use, or exclusions. An agent would have to infer usage from the name and context, which is insufficient for clear routing.

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