list_documents

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds useful behavioural context by explaining that results are grouped by employer/school and that group matching is a case-insensitive substring rather than an exact key. It does not say what form the downloadable items take (paths, URLs, counts) or what an empty group filter returns, so it goes beyond annotations but only modestly.

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?

Two short blocks: a front-loaded inventory of what is listed, then a compact Args section for the single optional parameter. Every sentence carries information and nothing is padded, though the prose inventory of document types is slightly listy relative to a one-parameter tool.

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?

With one optional parameter, an output schema present, and annotations covering safety, the description supplies what is missing: the content domain, the grouping semantics, and the filter matching rule. Return-value shape is rightly left to the output schema; only minor details (filter with no matches, ordering) are absent.

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?

Schema description coverage is 0%, so the description carries the full burden and does so well: it names concrete example group values ('Resume', 'MEARS', 'HP', 'Texas Tech', 'Other') and specifies case-insensitive substring matching, which the schema does not convey at all. It stops short of saying whether the filter is exact-group or matches any containing group name beyond the substring note.

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 a concrete resource set: downloadable resume formats plus portfolio artefacts (architecture diagrams, process docs, write-ups, certificates, lab reports) grouped by employer/school. That is far more specific than the bare name 'list_documents' and separates it from resume/profile siblings like get_experience or list_side_projects, though it never explicitly contrasts itself with the 'search' 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?

Usage is only implied: an agent can infer this is the browse-everything-documents tool while 'search' is the query-based one. There is no explicit when-to-use/when-not-to-use statement, no note that group filtering is a narrowing rather than a query, and no guidance on choosing this over 'search'.

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