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

With no annotations, the description does real work: it discloses result ordering, the fields returned, and a meaningful operational constraint — the share URL is not retrievable after creation, so this cannot be used to recover a link. It stops short of stating read-only semantics, permissions, or pagination behavior.

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 sentences, both earning their place: the first delivers scope plus return shape, the second delivers the non-obvious gotcha. Nothing is buried or padded.

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 single-parameter list tool with no output schema, the description covers what comes back and in what order, which is most of what an agent needs. Missing only access requirements and result-set bounds, which matters more here because no annotations exist to cover them.

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 single parameter has 0% schema description coverage, so the schema gives only a name and uuid format. 'on a job' implies job_id scopes the listing, but the description never states that the parameter is required or what happens with an unknown job.

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?

Specific verb+resource: lists photo share links scoped to a job, with ordering ('newest first') and the fields returned ('whether each is still active and how often it was opened'). It implicitly separates itself from shares_create (which would surface the link) via 'The link itself is not shown again', but never names a 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 read/inspect path for existing shares. There is no explicit when-to-use, no mention of shares_create for generating a link or shares_revoke for deactivating one, so routing between the three siblings is left to inference.

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