Audit profile

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

The description includes '[risk: read-only]' and 'No network calls to LinkedIn', clearly indicating a safe, non-destructive operation. Since no annotations are present, the description fully carries the burden and does so effectively.

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 concise (two sentences) and front-loaded with a risk annotation. However, it could include the parameter and output expectations without added length, so it loses a point for missing relevant information.

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 covers the tool's purpose and behavior well, but lacks the optional parameter targetRole and does not detail the output format (e.g., score ranges). Given no output schema, this additional context would enhance completeness.

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 has one optional enum parameter (targetRole) with 0% description coverage, but the description does not mention it at all. For a tool with a single parameter, this omission is a significant gap in usability.

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 tool reads and analyzes locally stored profile data and scores it for multiple dimensions. It distinguishes from sibling tools like get_profile_snapshot (retrieve) and export_profile_patch (export) by focusing on analysis and scoring.

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 implies use after obtaining a profile snapshot, noted by 'Score the saved profile snapshot'. It explicitly states no network calls, but it does not provide explicit when-not-to-use or alternatives among siblings.

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