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

Beyond the annotations, the description discloses ordering (newest first), the fields present on every entry, the absence of input, and important exclusions such as pay and confidential client details. Since there is no output schema, these details are especially valuable and give the agent a clear picture of what a successful call will contain.

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 front-loaded with the resource scope and ordering, then adds return fields, input behavior, exclusions, and sibling routing. Every sentence contributes useful information, and there is no unnecessary filler.

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 no output schema, the description is complete enough to call correctly. It explains the content, the shape of returned entries, the ordering, exclusions, and where to go for related data that is not returned here.

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, so the schema is inherently empty and the baseline is 4. The description reinforces this with “Takes no input,” which is useful confirmation but does not add parameter-level semantics beyond the absence of arguments.

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 the exact resource: work experience, leadership roles, and education, with specific parenthetical scopes like internships and student clubs. It also explicitly distinguishes this tool from get_achievements and list_projects, so an agent can immediately tell what this tool returns and what it does not.

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?

It states the intended content directly and gives explicit routing for adjacent needs: patents, awards, and certifications go to get_achievements, while projects go to list_projects. The exclusions and alternatives make selection between these common portfolio sections unambiguous.

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