get_public_share_by_slug_cover

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description only adds the HTTP method and path, and does not disclose additional behavior such as whether authentication is needed, what the response body is, or how errors are surfaced. It repeats safety information already encoded in annotations rather than extending it.

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 very short and front-loaded with the action, followed by the endpoint and a minimal argument note. There is no filler or redundancy, but the brevity comes at the cost of omitting the substantive context an agent would need.

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, read-only GET with an output schema, the endpoint and parameter placement are mostly enough for a basic call. However, the description lacks any context about what a share cover is, how the slug is obtained, or when this endpoint is preferable to sibling share endpoints. It is minimally adequate but not complete.

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 only parameter, slug, is described merely as 'Path parameter', which is syntactic rather than semantic. The schema itself has no description for slug, so with 0% schema coverage the description needed to explain what the slug represents, where it comes from, or how it is formatted. It does not.

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 clear verb and resource: 'Get share cover' and the HTTP route GET /public/share/{slug}/cover. It is not a tautology, but it does not explicitly distinguish itself from sibling share endpoints such as get_public_share_by_slug or get_public_share_by_slug_track_by_index beyond its name and path.

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?

There is no guidance about when to use this tool instead of the sibling share-related tools, no exclusions, and no mention of how this endpoint relates to the others. The agent must infer usage solely from the name and endpoint.

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